Commit Graph

8 Commits

Author SHA1 Message Date
briggs 9082432644 Go ahead and define xor function names up to xor16. 2003-11-07 22:04:59 +00:00
thorpej a2a587d698 Add a well-known dmover function name for the CRC32C used by the iSCSI
protocol.
2003-07-19 02:03:11 +00:00
thorpej 5f35784b8a Add immediate value support for dmoverio transactions. 2003-07-19 02:00:18 +00:00
thorpej 792ce8fe0d Fix typo in previous. 2003-06-14 19:03:40 +00:00
thorpej d0e1416b29 Separate out the immediate value from the input buffer. The immediate
value field can now always be used as an input, and output, or both.

This is especially handy for data movers which can e.g. calculate the
CRC32C of a buffer as it is moved (which requires both a seed [input],
and a place to stash the result [output]).
2003-06-12 17:20:43 +00:00
thorpej 16003abd0f Add standard names for 5-, 6-, 7-, and 8-way XOR. 2002-08-04 02:17:06 +00:00
thorpej 32ff91814a Add "xor2", "xor3", and "xor4" function names, which perform an
XOR on 2, 3, and 4 input streams, respectively.
2002-08-02 06:45:40 +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