| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
callout_deactivate().
PR: 192520
Submitted by: yaneurabeya gmail com
MFC after: 3 days
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
- Small mdoc fix.
Submitted by: pluknet
|
|
|
|
|
|
|
|
|
| |
with rmlocks. This works only with non-sleepable rm because handlers run
in SWI context. While here, document the new KPI in the timeout(9)
manpage.
Requested by: adrian, scottl
Reviewed by: mav, remko(manpage)
|
|
|
|
|
| |
Dcoument the new functions added to condvar(9), sleep(9), sleepqueue(9)
KPIs. Also document recent changes in timeout(9) and eventtimers(4).
|
| |
|
|
|
|
|
|
|
| |
their curcpu variants.
Discussed with: mav, davide
MFC after: 1 week
|
|
|
|
|
|
|
| |
Disussed with: gavin
No objection from: doc
Approved by: joel
MFC after: 3 days
|
|
|
|
| |
They have no effect when coming in pairs, or before .Bl/.Bd
|
| |
|
|
|
|
|
|
| |
their software.
Obtained from: NetBSD
|
|
|
|
|
|
| |
compatibility with other systems
Reviewed by: ed, battlez
|
|
|
|
|
| |
Requested by: attilio
Reviewed by: attilio
|
|
|
|
|
|
|
|
| |
- Reword a confusing sentence.
PR: docs/89810
Submitted by: Marius Nuennerich marius dot nuennerich at gmx dot net
MFC after: 3 days
|
| |
|
|
|
|
|
|
| |
was rescheduled. If there was no pending callout, then return 0.
Reviewed by: iedowse, cperciva
|
|
|
|
| |
Approved by: re
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
callout is first initialised, using a new function callout_init_mtx().
The callout system will acquire this mutex before calling the callout
function and release it on return.
In addition, the callout system uses the mutex to avoid most of the
complications and race conditions inherent in asynchronous timer
facilities, so mutex-protected callouts have much simpler semantics.
As long as the mutex is held when invoking callout_stop() or
callout_reset(), then these functions will guarantee that the callout
will be stopped, even if softclock() had already begun to process
the callout.
Existing Giant-locked callouts will automatically pick up the new
race-free semantics. This should close a number of race conditions
in the USB code and probably other areas of the kernel too.
There should be no change in behaviour for "MP-safe" callouts; these
still need to use the techniques mentioned in timeout(9) to avoid
race conditions.
|
|
|
|
| |
Uncompact enumaration to make it look better.
|
|
|
|
|
|
| |
when using the callout subsystem. Show how the callout_pending(),
callout_active() and callout_deactivate() macros can be used to
achieve simpler race-free callout semantics in many situations.
|
|
|
|
| |
MFC after: 1 week
|
| |
|
|
|
|
|
|
| |
* correctly place parenthisized sentences
* remove hard sentence breaks
* use .Vt instead of .Fn
|
|
|
|
|
|
|
|
|
|
|
| |
callout_stop(), except that if the callout being stopped is currently
in progress, it blocks attempts to reset the callout and waits until the
callout is completed before it returns.
This makes it possible to clean up callout-using code safely, e.g.,
without potentially freeing memory which is still being used by a callout.
Reviewed by: mux, gallatin, rwatson, jhb
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
callout lock while the callout is happening. So the serialization
that I thought was happening isn't. Therefore, remove the part of the
bugs that says this. Leave in the other bug as it is very hard to
work around (impossible?).
Fix various typos.
Also note that timeout/untimeout are considered to be the old interface and
the callout interface should be used insetad.
Submitted by: bde (first two) and wollman (third)
|
|
|
|
|
|
|
| |
callout has finished or is in progress. Also document that the
locking of the callout code for FreeBSD 5 has eliminated the 'or is in
progress' clause as a possibility and that such elimination is an
accident of the implementation and shouldn't be relied upon.
|
| |
|
|
|
|
|
| |
describe it.
- Add a return values section.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
cd src/share; find man[1-9] -type f|xargs perl -pi -e 's/[ \t]+$//'
BTW, what editors are the culprits? I'm using vim and it shows
me whitespace at EOL in troff files with a thick blue block...
Reviewed by: Silence from cvs diff -b
MFC after: 7 days
|
| |
|
|
|
|
|
|
| |
PR: 24529
Submitted by: harti brandt <brandt@fokus.gmd.de>
Reviewed by: jlemon
|
| |
|
| |
|
|
|
|
| |
create links to functions so added found.
|
|
|
|
|
|
|
|
| |
spl0) and some bitrot (the not-so-new callout_init/stop/reset functions
were not mentioned; the callout_activate/deactivate/pending macros are
still not mentioned).
Submitted by: mostly by jlemon
|
| |
|
|
|
|
| |
based version over the top of the FreeBSD version in rev.1.6.
|
|
|
|
| |
man page was based on the NetBSD version.
|
| |
|
|
|
|
|
| |
Nuked the confusing timeout_func_t typedef. It will go away in <systm.h>
later.
|
| |
|
|
|
|
|
|
|
|
| |
This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been
insane otherwise.
|
|
|