On Fri, Aug 29, 2008 at 02:41:01AM +0900, Tejun Heo wrote:

quoted text
> ioctl support is tricky to implement because only the ioctl

> implementation itself knows which memory regions need to be read

> and/or written.  To support this, fuse client can request retry of

> ioctl specifying memory regions to read and write.  Deep copying

> (nested pointers) can be implemented by retrying multiple times

> resolving one depth of dereference at a time.

Why do we need ioctls?  For CUSE?  In that case, would we need to copy

the memory from userspace, into the kernel, and then back out into

userspace again?  Can't we just have a "pass-through" type fixed ioctl

instead?
thanks,
greg k-h

--

unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

the body of a message to majordomo@vger.kernel.org

More majordomo info at  http://vger.kernel.org/majordomo-info.html

Please read the FAQ at  http://www.tux.org/lkml/