[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, Aug 28, 2008 at 08:02:44PM +0200, 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, but frankly, at this point, I think that would
> be an premature optimization.

No, I'm not worried about the performance, just that this should be
simple as we can just pass "arg" to userspace without touching it as it
just came from userspace, right?

Oh wait, there are process space issues at play here that I'm totally
forgetting about, right?


greg k-h

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