> > 	- fill region by random number (easy)
>I think for hardware devices that can provide random numbers, what we
>really want is for them to feed into the kernel's entropy pool.  In most
>cases where we want a block of random data (e.g. IV's), the amount of
>data we want isn't going to justify the overhead of using dmover.  (One
>of the biggest advantages of dmover is that it's asynchronous, so you can
>do other work while you're waiting for your RAID parity to be computed.)
>
>Did you have something else in mind for a "rand-block" dmover function?

	i can see your point.  i don't have "rand-block big chunk of memory"
	example in my hand, but anyways, it can be done with rnd(4) output.

>Actually, I have a separate framework for data transformations like ciphers
>(or MPEG encode/decode, etc.).  I originally wanted to have them handled by
>the same framework, but there were some interface issues that were too
>difficult to solve:
(snip)
>I will post more about the xform facility soon (I haven't written any
>documentation for it yet :-)

	good good:-)

itojun