From: Matt Mackall <mpm@selenic.com>
To: Christensen Tom <paveraware@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Network Performance Ingo's RT-Preempt
Date: Wed, 30 Mar 2005 00:42:09 -0800 [thread overview]
Message-ID: <20050330084209.GF25554@waste.org> (raw)
In-Reply-To: <BAY104-F21CE6F100043D58186803FDF430@phx.gbl>
On Sun, Mar 27, 2005 at 10:27:40PM +0000, Christensen Tom wrote:
> I'm running 2.6.11 with Ingo's Preempt patch
> (realtime-preempt-2.6.11-final-V0.7.40-04). The system is SMP with a
> broadcom NIC (tg3 driver). I am seeing truly appalling network performance
> (2-4kbps on a 1gbps network). Is this a known issue? I know this patch is
> not production ready, what traces/logs do you need/want to be able to
> debug/fix this?
What is your test app and what protocol does it use?
What performance do you get with mainline?
A tcpdump log is probably a good place to start. You might consider
cc:ing Ingo and possibly netdev.
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2005-03-30 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 22:27 Network Performance Ingo's RT-Preempt Christensen Tom
2005-03-30 8:42 ` Matt Mackall [this message]
2005-03-30 8:58 ` Lee Revell
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=20050330084209.GF25554@waste.org \
--to=mpm@selenic.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paveraware@hotmail.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.