Hi!
> > > > Why? I think that either whole device needs GFP_NOIO or whole device
> > > > can live with GFP_KERNEL, but I can't imagine a device where aprt needs
> > > > GFP_NOIO and part does not...
> > >
> > > I can imagine a device that includes both a usb-storage
> > > interface, used for swapping/paging/etc, and other
> > > interfaces (say, for audio/video I/O streams). Would
> > > that suit as one example, or would you insist on being
> > > able to buy one first? :)
> >
> > Well, buy one first, and if GFP_NOIO hurts on it (it probably will
> > not), we'll care?
>
> Can we agree that in the lifetime of 2.4 we can live with a device specific
> flag ? I think with this flag usb storage can be made safe and even swap made
> possible unless you use ethernet.
>
> > > Or with a single usb-storage interface, and vendor-specific
> > > control messages used to tweak something from a usermode
> > > tool; there's no reason to have the usermode calls use NOIO,
> > > but control messages to clear error status during paging will
> > > need it.
> >
> > Yep, but NOIO does not really hurt unless you use it way too much.
>
> A combination of mass storage and a video camera seems certainly possible.
> IMHO we should not cripple our API.
Okay, that seems reasonable (and is called digital photoaparaturus).
>
> By the way do you want to test code to enable swapping over usb
> storage ?
If you have such code, send it my way.
>
> Regards
> Oliver
--
The best software in life is free (not shareware)! Pavel
GCM d? s-: !g p?:+ au- a--@ w+ v- C++@ UL+++ L++ N++ E++ W--- M- Y- R+
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
