From: Mike Galbraith <efault@gmx.de>
To: bert hubert <bert.hubert@netherlabs.nl>
Cc: Con Kolivas <kernel@kolivas.org>,
lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@osdl.org>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Peter Williams <pwil3058@bigpond.net.au>
Subject: Re: [patch][rfc] quell interactive feeding frenzy
Date: Sun, 09 Apr 2006 20:07:41 +0200 [thread overview]
Message-ID: <1144606061.7408.14.camel@homer> (raw)
In-Reply-To: <20060409121436.GA28075@outpost.ds9a.nl>
On Sun, 2006-04-09 at 14:14 +0200, bert hubert wrote:
> On Sun, Apr 09, 2006 at 01:39:38PM +0200, Mike Galbraith wrote:
> > Ok, unusable may be overstated. Nonetheless, that bit of code causes
> > serious problems. It makes my little PIII/500 test box trying to fill
> > one 100Mbit local network unusable. That is not overstated.
>
> If you try to make a PIII/500 fill 100mbit of TCP/IP using lots of different
> processes, that IS a corner load.
>
> I'm sure you can fix this (rare) workload but are you very sure you are not
> killing off performance for other situations?
Rare? What exactly is rare about a number of tasks serving data? I
don't care if it's a P4 serving gigabit. If you have to divide your
server into pieces (you do, and you know it) you're screwed.
> I get flashbacks to the old days of the VM where we had lots patches around
> that would all solve (more or less) real problems, but never all at the same
> time..
I choose to take the high road here, and will not respond.
-Mike
next prev parent reply other threads:[~2006-04-09 18:06 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 9:38 [patch][rfc] quell interactive feeding frenzy Mike Galbraith
2006-04-07 9:47 ` Andrew Morton
2006-04-07 9:52 ` Ingo Molnar
2006-04-07 10:57 ` Mike Galbraith
2006-04-07 11:00 ` Con Kolivas
2006-04-07 11:09 ` Mike Galbraith
2006-04-07 10:40 ` Mike Galbraith
2006-04-07 12:56 ` Con Kolivas
2006-04-07 13:37 ` Mike Galbraith
2006-04-07 13:56 ` Con Kolivas
2006-04-07 14:14 ` Mike Galbraith
2006-04-07 15:16 ` Mike Galbraith
2006-04-09 11:14 ` bert hubert
2006-04-09 11:39 ` Mike Galbraith
2006-04-09 12:14 ` bert hubert
2006-04-09 18:07 ` Mike Galbraith [this message]
2006-04-10 9:12 ` bert hubert
2006-04-10 10:00 ` Mike Galbraith
2006-04-10 14:56 ` Mike Galbraith
2006-04-13 7:41 ` Mike Galbraith
2006-04-13 10:16 ` Con Kolivas
2006-04-13 11:05 ` Mike Galbraith
2006-04-09 18:24 ` Mike Galbraith
-- strict thread matches above, loose matches on Subject: below --
2006-04-09 16:44 Al Boldi
2006-04-09 18:33 ` Mike Galbraith
2006-04-10 14:43 ` Al Boldi
2006-04-11 10:57 ` Con Kolivas
[not found] <200604112100.28725.kernel@kolivas.org>
2006-04-11 17:03 ` Fwd: " Al Boldi
2006-04-11 22:56 ` Con Kolivas
2006-04-12 5:41 ` Al Boldi
2006-04-12 6:22 ` Con Kolivas
2006-04-12 8:17 ` Al Boldi
2006-04-12 9:36 ` Con Kolivas
2006-04-12 10:39 ` Al Boldi
2006-04-12 11:27 ` Con Kolivas
2006-04-12 15:25 ` Al Boldi
2006-04-13 11:51 ` Con Kolivas
2006-04-14 3:16 ` Al Boldi
2006-04-15 7:05 ` Con Kolivas
2006-04-15 20:45 ` Al Boldi
2006-04-15 23:22 ` Con Kolivas
2006-04-16 6:02 ` Con Kolivas
2006-04-16 8:31 ` Al Boldi
2006-04-16 8:58 ` Con Kolivas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1144606061.7408.14.camel@homer \
--to=efault@gmx.de \
--cc=akpm@osdl.org \
--cc=bert.hubert@netherlabs.nl \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=pwil3058@bigpond.net.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.