From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Ben Greear <greearb@candelatech.com>
Cc: Christian Schmid <webmaster@rapidforum.com>,
linux-kernel@vger.kernel.org
Subject: Re: BUG: Slowdown on 3000 socket-machines tracked down
Date: Mon, 07 Mar 2005 20:28:32 +1100 [thread overview]
Message-ID: <422C1EC0.8050106@yahoo.com.au> (raw)
In-Reply-To: <422C1D57.9040708@candelatech.com>
Ben Greear wrote:
> Nick Piggin wrote:
>
>> Ben Greear wrote:
>>
>> In that case, writing the network only test would help to confirm the
>> problem is not a networking one - so not useless by any means.
>
>
> It's not trivial to write something like this :)
>
> I'll be using something I already have. If I can't reproduce the problem,
> then perhaps it is due to sendfile and someone can write a customized
> test. The main reason I offered is because people are ignoring the
> bug report for the most part and asking for a test case. I may be able
> to offer an independent verification of the problem which might convince
> someone to write up a dedicated test case...
>
OK, no that sounds good, please do make the test case.
I have actually been following up with Christian regarding
the disk IO / memory management side of things but the thread
has gone offline for some reason :\
next prev parent reply other threads:[~2005-03-07 9:31 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 17:10 BUG: Slowdown on 3000 socket-machines tracked down Christian Schmid
2005-03-07 0:45 ` Nick Piggin
2005-03-07 1:13 ` Ben Greear
2005-03-07 1:58 ` Christian Schmid
2005-03-07 2:57 ` Ben Greear
2005-03-07 5:14 ` Nick Piggin
2005-03-07 5:30 ` Willy Tarreau
2005-03-07 5:41 ` Nick Piggin
2005-03-07 5:42 ` Nick Piggin
2005-03-07 5:46 ` Willy Tarreau
2005-03-07 9:22 ` Ben Greear
2005-03-07 9:28 ` Nick Piggin [this message]
2005-03-08 6:30 ` Ben Greear
2005-03-08 16:41 ` Christian Schmid
2005-03-09 23:45 ` Ben Greear
2005-03-09 23:52 ` Christian Schmid
2005-03-10 0:18 ` Ben Greear
2005-03-10 0:24 ` Christian Schmid
2005-03-10 5:17 ` Andrew Morton
2005-03-10 9:00 ` Andi Kleen
2005-03-10 9:09 ` Andrew Morton
2005-03-10 9:12 ` Andi Kleen
2005-03-10 9:38 ` Andrew Morton
2005-03-10 19:03 ` Ben Greear
2005-03-10 18:51 ` Christian Schmid
2005-03-10 19:06 ` Christian Schmid
2005-03-11 15:29 ` Christian Schmid
2005-03-11 19:10 ` Ben Greear
2005-03-11 19:27 ` Christian Schmid
2005-03-14 4:40 ` Nick Piggin
2005-03-14 4:53 ` Christian Schmid
2005-03-14 5:04 ` Nick Piggin
2005-05-28 3:17 ` Christian Schmid
2005-06-08 2:26 ` Christian Schmid
2005-06-08 2:39 ` Nick Piggin
2005-06-08 2:44 ` Andrew Morton
2005-03-07 14:35 ` Christian Schmid
2005-03-07 23:37 ` Ben Greear
2005-03-07 2:07 ` Christian Schmid
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=422C1EC0.8050106@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=webmaster@rapidforum.com \
/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.