Commit Graph

9 Commits

Author SHA1 Message Date
jakllsch
3af888c194 Convert remaining simplelock usage in dmover(4) to a RUN_ONCE(9). 2011-05-14 18:24:47 +00:00
matt
acb0b175a3 Add #include <sys/simplelock.h> 2008-01-05 02:47:03 +00:00
ad
598ab03ad0 Match the docs: MUTEX_DRIVER/SPIN are now only for porting code written
for Solaris.
2007-12-05 07:06:50 +00:00
ad
88ab7da936 Merge some of the less invasive changes from the vmlocking branch:
- kthread, callout, devsw API changes
- select()/poll() improvements
- miscellaneous MT safety improvements
2007-07-09 20:51:58 +00:00
briggs
4c104c6cea In dmover_backend_alloc(), make sure we get ninputs from the best_algdesc,
not just the most recent algdesc (which might be NULL).
2003-04-26 04:44:18 +00:00
briggs
cb2eb4a01a Mmmm... LOCKDEBUG...
Change from unlock -> modify -> unlock to _lock_ -> modify -> unlock.
2003-04-01 20:59:15 +00:00
thorpej
18e5ffe231 Fix typo. 2002-12-28 23:07:18 +00:00
thorpej
ff8c9fb45c Grr, fix typo in RCS ID tag. 2002-08-02 00:31:35 +00:00
thorpej
5d06c0e812 dmover(9) -- an interface to hardware-assisted data movers. This allows
clients to use a hardware-assisted data mover to clear a region of memory,
fill a region of memory with a specific value, copy a region of memory,
and perform simple boolean operations such as XOR on multiple regions
of memory.

Included here is a software back-end which can serve as an example of
how to write a back-end (and also provides a fall-back in case hardware
for a given function is not available), as well as a dmoverio(4) pseudo-
device which provides access to dmover(9) to userland via a message
passing interface.

dmover(9) is still a work-in-progress -- a few minor changes to the
interface are expected.
2002-08-02 00:30:37 +00:00