History log of /netbsd-src/sys/dev/dmover/dmover_backend.c (Results 1 – 9 of 9)
Revision Date Author Comments
# 3af888c1 14-May-2011 jakllsch <jakllsch@NetBSD.org>

Convert remaining simplelock usage in dmover(4) to a RUN_ONCE(9).


# acb0b175 05-Jan-2008 matt <matt@NetBSD.org>

Add #include <sys/simplelock.h>


# 598ab03a 05-Dec-2007 ad <ad@NetBSD.org>

Match the docs: MUTEX_DRIVER/SPIN are now only for porting code written
for Solaris.


# 88ab7da9 09-Jul-2007 ad <ad@NetBSD.org>

Merge some of the less invasive changes from the vmlocking branch:

- kthread, callout, devsw API changes
- select()/poll() improvements
- miscellaneous MT safety improvements


# 4c104c6c 26-Apr-2003 briggs <briggs@NetBSD.org>

In dmover_backend_alloc(), make sure we get ninputs from the best_algdesc,
not just the most recent algdesc (which might be NULL).


# cb2eb4a0 01-Apr-2003 briggs <briggs@NetBSD.org>

Mmmm... LOCKDEBUG...
Change from unlock -> modify -> unlock to _lock_ -> modify -> unlock.


# 18e5ffe2 28-Dec-2002 thorpej <thorpej@NetBSD.org>

Fix typo.


# ff8c9fb4 02-Aug-2002 thorpej <thorpej@NetBSD.org>

Grr, fix typo in RCS ID tag.


# 5d06c0e8 02-Aug-2002 thorpej <thorpej@NetBSD.org>

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

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.

show more ...