lkml.org 
[lkml]   [1998]   [Jul]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Strange interrupt behaviour


On Thu, 16 Jul 1998, Rogier Wolff wrote:
>
> The "right" way to handle this, is to make kmalloc/gfp/whatever
> implement this, and allow just a few places to set the flag that
> enables getting stuff from the "last resort" pool.

The problem with that is that we really want to have multiple
"last-resort" pools.

For example, NFS would probably also be happier with a last-resort pool
for kmallocs (of both 8kB and 16kB allocations - we don' tneed a very deep
pool, just 2-4 allocations would probably be fine to handle the bad
cases), but we do _not_ want to allow NFS starvation to starve fork()'s or
vice versa.

I certainly agree with making this a more generic thing, but it mustn't be
just a flag that everybody then fights over.

Kubys


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html

\
 
 \ /
  Last update: 2005-03-22 13:43    [W:0.717 / U:0.092 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site