![]() | |||||||||||
Messages in this thread |
Am Freitag, 20. August 2004 04:37 schrieb Nick Piggin: > So if this thing allocates memory on behalf of a read request, then > it is basically a bug. In practice you could probably get away with > servicing all writes with PF_MEMALLOC, however that could still lead > to situations where it consumes all your low memory on behalf of > highmem IO (though perhaps this won't deadlock if that memory is > going to be released as a matter of course?) > > Another thing, having it always use PF_MEMALLOC means it can easily > wipe out the GFP_ATOMIC reserve. > > So I'd say try to find a way to only use PF_MEMALLOC on behalf of > a PF_MEMALLOC thread or use a mempool or something. Then the SCSI layer should pass down the flag. Regards Oliver - 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/ | ||||||||||
| Last update: 2005-03-22 14:05 [from the cache] ©2003-2008 | |||||||||||