[lkml]   [2008]   [Aug]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 5/7] FUSE: implement ioctl support
On Fri, Aug 29, 2008 at 02:41:01AM +0900, Tejun Heo wrote:
> 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


greg k-h

 \ /
  Last update: 2008-08-28 19:57    [W:0.133 / U:2.468 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site