At this point, I think the "best" answer is to say:

        Don't swap over USB for a 2.4.x kernel.

I think this issue is better addressed in 2.5, for stability reasons.

Matt

On Tue, Sep 18, 2001 at 11:57:02PM +0200, Oliver Neukum wrote:
> Am Dienstag, 18. September 2001 18:59 schrieb Alan Cox:
> > > Some USB APIs will be trouble, since they don't pass an URB
> > > or explicit mem_flags value down.  Were you thinking of just
> > > making it all use SLAB_NOIO?  That might cause a few more
> > > "out of memory" error reports in places it's not necessary (khubd
> > > as one example).  But I'm not sure making usb_control_msg() and
> > > all its callers (and their callers ... :) take a new mem_flags parameter
> > > would be a reasonable API change.
> >
> > Would it be better to make the memory type to use a device flag on the
> > device we are throwing the urb at ?
> 
> Strictly speaking the requirement is not device specific.
> An additional parameter, if extended to usb_submit_urb(), has the added bonus 
> that there's no longer a problem of deciding whether to allocate memory 
> atomically.
> How detrimental is GFP_NOIO to the VM ?
>       Regards
>               Oliver

-- 
Matthew Dharm                              Home: [EMAIL PROTECTED] 
Maintainer, Linux USB Mass Storage Driver

You should try to see the techs say "three piece suit".
                                        -- The Chief
User Friendly, 11/23/1997

PGP signature

Reply via email to