[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 Thu, 28 Aug 2008, Tejun Heo wrote:
> Tejun Heo wrote:
> > Greg KH wrote:
> >> 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?
> >
> > Can you elaborate a bit? How the fixed ioctl would know how much to
> > copy in and out and from where?
> If you're worried about the double copying due to performance reasons,
> what we can do is implementing userspace to userspace copying. I just
> took easier path of copying twice as u-u copy can't be done using the
> existing FUSE mechanics.

How about not copying anything in the kernel, just passing the virtual
address to the filesystem? It can get/modify the data of the calling
task by mapping /proc/pid/mem. Ugly, yes, but ioctls are inherently


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