lkml.org 
[lkml]   [1998]   [Aug]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Notebooks
Date
  torvalds@transmeta.com (Linus Torvalds) writes:
>
> In this case, TCP wanted to allocate a single skb, and due to slabs this
> got turned into a multi-page request even though it fit perfectly fine
> into one page. Thus a critical allocation could fail, and the TCP layer
> started looping - and kswapd could never even try to fix it up because
> the TCP code held the kernel lock.
>
Methinks that TCP ought to be able to recover from out-of-memory conditions,
just like any other part of the kernel. If slabs make those things which
fall over when they don't get their memory fall over more often, that's
fine with me: it means we get to find more bugs. ;-)

Sure, 2.2 should probably behave differently, but we're not there yet...

--
Matthias Urlichs
noris network GmbH

-
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:44    [from the cache]
©2003-2011 Jasper Spaans