From: Christian Schmid <webmaster@rapidforum.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@oss.sgi.com
Subject: Re: Bug-hunting
Date: Wed, 23 Feb 2005 11:28:24 +0100 [thread overview]
Message-ID: <421C5AC8.70601@rapidforum.com> (raw)
In-Reply-To: <20050222193000.404ae6d2.davem@davemloft.net>
I would have to write a test-program first. This needs time. Before I spend hours into coding this,
first just tell me how I can raise the global-limit from around 600-700 MB to 1500 MB.
David S. Miller wrote:
> On Wed, 23 Feb 2005 00:21:31 +0100
> Christian Schmid <webmaster@rapidforum.com> wrote:
>
>
>>To reproduce this, you would have to create a server which is sending data to 4000 non-blocking
>>sockets. It doesnt matter what you send. You should realize a slow-down the more sockets you use.
>>You need Gigabit for this to appear.
>
>
> Please send us the exact test programs to run, not some general
> description of what "one should do" to reproduce the problem.
>
> This is exactly what is stalling this bug getting diagnosed properly
> and fixed.
>
>
next prev parent reply other threads:[~2005-02-23 10:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 15:07 Bug-hunting Christian Schmid
2005-02-22 18:44 ` Bug-hunting David S. Miller
2005-02-22 19:17 ` Bug-hunting Christian Schmid
2005-02-22 19:51 ` Bug-hunting David S. Miller
2005-02-22 23:21 ` Bug-hunting Christian Schmid
2005-02-23 3:30 ` Bug-hunting David S. Miller
2005-02-23 10:28 ` Christian Schmid [this message]
2005-02-23 19:29 ` Bug-hunting David S. Miller
2005-02-23 19:41 ` Bug-hunting Christian Schmid
2005-02-23 19:53 ` Bug-hunting David S. Miller
2005-02-23 19:46 ` Bug-hunting Christian Schmid
2005-02-23 20:00 ` Bug-hunting John Heffner
2005-02-24 12:29 ` Bug-hunting 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=421C5AC8.70601@rapidforum.com \
--to=webmaster@rapidforum.com \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.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.