From: Ben Greear <greearb@candelatech.com>
To: danial_thom@yahoo.com
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.12 Performance problems
Date: Thu, 25 Aug 2005 09:55:27 -0700 [thread overview]
Message-ID: <430DF7FF.9080502@candelatech.com> (raw)
In-Reply-To: <20050825142647.70995.qmail@web33314.mail.mud.yahoo.com>
Danial Thom wrote:
> The tests I reported where on UP systems. Perhaps
> the default settings are better for this in 2.4,
> since that is what I used, and you used your
> hacks for both.
My modifications to the kernel are unlikely to speed anything
up, and probably will slow things down ever so slightly.
I can try with a UP kernel, but my machine at least has a single
processor. I'm using the SMP kernel to take advantage of HT.
> Are you getting drops or overruns (or both)? I
> would assume drops is a decision to drop rather
> than an overrun which is a ring overrun. Overruns
> would imply more about performance than tuning,
> I'd think.
I was seeing lots of NIC errors...in fact, it was showing a great many
more errors than packets sent to it, so I just ignored them.
I increased the TxDescriptors and RxDescriptors and that helped a little.
Increasing the transmit queue for the NIC to 2000 also helped a little.
> I wouldn't think that HT would be appropriate for
> this sort of setup...?
2.6.11 seems to be faster when running SMP kernel on this system.
>
> You're using a dual PCI-X NIC rather than the
> onboard ports? Supermicro runs their onboard
Of course. Never found a motherboard yet with decent built-in
NICs. The built-ins on this board are tg3 and they must be on
a slow bus, because they cannot go faster than about 700Mbps
(using big pkts).
I'll benchmark things again when 2.6.13 comes out and try to
get some more detailed numbers...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2005-08-25 16:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050824172631.11829.qmail@web33309.mail.mud.yahoo.com>
2005-08-25 4:51 ` 2.6.12 Performance problems Ben Greear
2005-08-25 6:08 ` Danial Thom
2005-08-25 6:15 ` Ben Greear
2005-08-26 3:29 ` Danial Thom
2005-08-26 22:18 ` Danial Thom
2005-08-25 6:34 ` Ben Greear
2005-08-25 14:26 ` Danial Thom
2005-08-25 16:55 ` Ben Greear [this message]
2005-08-25 20:45 ` Danial Thom
2005-08-26 19:10 ` Benjamin LaHaise
2005-08-27 11:19 ` Vladimir B. Savkin
2005-08-27 14:35 ` Danial Thom
[not found] <20050821154654.63788.qmail@web33303.mail.mud.yahoo.com>
2005-08-21 19:47 ` Andrew Morton
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=430DF7FF.9080502@candelatech.com \
--to=greearb@candelatech.com \
--cc=danial_thom@yahoo.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).