Miklos Szeredi wrote:
quoted text
> On Fri, 21 Nov 2008, Tejun Heo wrote:
>>> I removed ->unrestricted_ioctl() and associated code because it really
>>> doesn't make any sense: the high level lib won't be used for CUSE
>>> stuff, otherwise unrestrited ioctls are not allowed (and the interface
>>> is rather horrible anyway).
>> Well, CUSE highlevel interface piggy backs on FUSE so it requires
>> unrestricted_ioctl() there for it and ossp does use it.
> 
> I thought it uses the lowlevel interface.  Why doesn't it do that?

Well, because it's simpler that way and people would be more used to it?
 It's just easier when you implement a method which returns something
and looks similar to the respective file operation.

quoted text
> For CUSE there's really no point in going through high level
> interface, since there's just one file involved, so the path name
> generation (the main feature of the highlevel lib) doesn't make any
> sense.

Well, the choice was mostly for convenience as there also are a few
places where high level interface wraps things better a bit.  Converting
wouldn't be difficult.  Do you think it's important?  I think keeping
things as parallel to FUSE as possible is more important.

Thanks.

-- 
tejun
--
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/