Re: Helping out with autosuspend

On Fri, Sep 14, 2007 at 10:31:18AM -0700, Sarah Sharp wrote:
> I talked with Zack Brown yesterday about AIO and syslets.  We worked out
> that usbfs2 could work with syslets, with a slight modification to the
> syslet API.  The user could set a flag to tell the syslet interface not
> to clone if the operation blocks; usbfs2 could make a function call
> after it submits the URB to let the syslet code know that it's ok to
> clone after that point.  This would solve the data reordering problem,
> which was the only reason I didn't like syslets.
> 
> It's not perfect, since it requires the user to know they need this
> special flag.  It would be great to put the flag in the file struct, but
> syslets have no knowledge of files; syslets only know about operations.
> 
> I'm not sure what to do with usbfs2 until syslets are in-tree.  I could
> implement it with in-kernel AIO, but without the troublesome cancel
> functionality.  Would you accept that, or should I work under the
> assumption that usbfs2 will be released when syslets are?

I think we should work with what is currently in the tree, and your AIO
patch as it fixes a real bug.  syslets are cool, but probably a year or
so away from being in the tree, right?

It's kind of funny the only users of AIO are huge Oracle instances, and
the tiny USB gadget filesystem :)

So, feel free to resubmit your patches for inclusion.

thanks,

greg k-h

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel