How would tying it to devices work? Starting to swap onto a file
would need to trigger that, also I/O to memory mapped files (yes?);
and it'd nice to be able to clear such device flags later. I don't know
what information the MM subsystem exports, or when it does so;
though I suppose usb-storage could set that flag for all disks, just
in case they're later used for swapping/paging.
I'm happy to avoid creating much policy flexibility (error prone
at that level!). And likely any system where a per-device policy
behaves much differently from a per-request policy is going to
be having some issues anyway ... :)
- Dave
----- Original Message -----
From: "Alan Cox" <[EMAIL PROTECTED]>
Sent: Tuesday, September 18, 2001 9:59 AM
Subject: Re: [linux-usb-devel] Re: usb-storage not suitable for swapping
> > 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 ?
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
