From: David Miller <davem@davemloft.net>
To: yevgenyp@mellanox.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 1/3] mlx4_en: TX ring size default to 1024
Date: Fri, 24 Feb 2012 15:14:15 -0500 (EST) [thread overview]
Message-ID: <20120224.151415.831305774793653355.davem@davemloft.net> (raw)
In-Reply-To: <953B660C027164448AE903364AC447D2618B8768@MTLDAG02.mtl.com>
From: Yevgeny Petrilin <yevgenyp@mellanox.com>
Date: Fri, 24 Feb 2012 19:35:45 +0000
> On the other hand, when having smaller queue with 1000 in-flight
> packets would mean queue would be stopped, how is it better?
It's a thousand times better.
Because if a high priority packet gets queued up it won't have to wait
for 1024 packets to hit the wire before it can go out.
You need to support byte queue limits before you jack things up so high
like this, otherwise high priority packets are absolutely pointless
and unusable.
next prev parent reply other threads:[~2012-02-24 20:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 13:34 [PATCH net-next 1/3] mlx4_en: TX ring size default to 1024 Yevgeny Petrilin
2012-02-23 19:45 ` David Miller
2012-02-23 19:54 ` Eric Dumazet
2012-02-24 19:35 ` Yevgeny Petrilin
2012-02-24 20:14 ` David Miller [this message]
2012-02-24 20:17 ` Eric Dumazet
2012-02-25 6:51 ` Bill Fink
2012-02-25 8:22 ` Eric Dumazet
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=20120224.151415.831305774793653355.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=yevgenyp@mellanox.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