From: Stephen Hemminger <shemminger@vyatta.com>
To: David Miller <davem@davemloft.net>
Cc: ron.mercer@qlogic.com, netdev@vger.kernel.org
Subject: Re: [net-next PATCH 3/3] qlge: Increase default TX/RX ring size to 1024.
Date: Thu, 11 Jun 2009 08:34:19 -0700 [thread overview]
Message-ID: <20090611083419.4c173558@nehalam> (raw)
In-Reply-To: <20090611.022713.35602614.davem@davemloft.net>
On Thu, 11 Jun 2009 02:27:13 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> From: Ron Mercer <ron.mercer@qlogic.com>
> Date: Wed, 10 Jun 2009 18:49:35 -0700
>
> >
> > Signed-off-by: Ron Mercer <ron.mercer@qlogic.com>
>
> This is huge. Even other aggressive NICs such as BNX2X only use 256
> ring entries per TX queue.
>
> There is a point where increasing definitely hurts, because you're
> increasing the resident set size of the cpu, as more and more SKBs are
> effectively "in flight" at a given time and only due to the amount
> you're allowing to get queued up into the chip.
>
> And with multiqueue, per-queue TX queue sizes should matter less at
> least to some extent.
>
> Are you sure that jacking the value up this high has no negative side
> effects for various workloads?
I am investigating reducing the sky2 default tx ring size down to
128 after user complaints about the latency. At 10G 1024 ring
entries is 7ms for jumbo frames.
next prev parent reply other threads:[~2009-06-11 15:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 1:49 [net-next PATCH 1/3] qlge: Relax alignment on TX harware queue Ron Mercer
2009-06-11 1:49 ` [net-next PATCH 2/3] qlge: Allow RX buf rings to be > than 4096 bytes Ron Mercer
2009-06-11 9:37 ` David Miller
2009-06-11 1:49 ` [net-next PATCH 3/3] qlge: Increase default TX/RX ring size to 1024 Ron Mercer
2009-06-11 9:27 ` David Miller
2009-06-11 15:34 ` Stephen Hemminger [this message]
2009-06-11 23:21 ` Ron Mercer
2009-06-11 23:50 ` David Miller
2009-06-11 9:37 ` [net-next PATCH 1/3] qlge: Relax alignment on TX harware queue David Miller
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=20090611083419.4c173558@nehalam \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=ron.mercer@qlogic.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 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).