lkml.org 
[lkml]   [1998]   [Aug]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Notebooks
On 19 Aug 1998, Matthias Urlichs wrote:

> 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...

With higher and higher speed networks becoming available, I predict that
sooner or later Linux networking is going to have to do what other high-
speed communications systems have been doing for years. If you don't
have space available for data packets, you dump them on the floor.

They will get sent again. In fact, this becomes a very workable throttle.
I hear over and over again from Linux Software developers that this
is considered "evil". Think this over again. There is nothing evil
about keeping the system alive.

Cheers,
Dick Johnson
***** FILE SYSTEM WAS MODIFIED *****
Penguin : Linux version 2.1.115 on an i586 machine (66.15 BogoMips).
Warning : It's hard to remain at the trailing edge of technology.

-
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-2014 Jasper Spaans. Advertise on this site