From: Geoff Kuenning <geoff@cs.hmc.edu>
To: Ming Chen <v.mingchen@gmail.com>
Cc: John Fastabend <john.fastabend@gmail.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
netdev@vger.kernel.org, Erez Zadok <ezk@fsl.cs.sunysb.edu>,
Dean Hildebrand <dhildeb@us.ibm.com>
Subject: Re: [BUG?] ixgbe: only num_online_cpus() of the tx queues are enabled
Date: Mon, 10 Mar 2014 21:56:31 -0700 [thread overview]
Message-ID: <pnizjkxxri8.fsf@bow.cs.hmc.edu> (raw)
In-Reply-To: <CAG+wggY+Ya1ehtAF9ZF=wkq7aQ9jgsQOB-Nj0ZwQhJWTMs3PQA@mail.gmail.com> (Ming Chen's message of "Sun, 9 Mar 2014 01:56:18 -0500")
> In our case, we believe larger number of tx queues will reduce the
> probability of hash collision.
However, that's only true for fairly small numbers of flows. If you
have 64 queues and 65 flows then two of the flows are guaranteed to
collide in the best case.
Not that I have a brilliant solution, just pointing it out...
--
Geoff Kuenning geoff@cs.hmc.edu http://www.cs.hmc.edu/~geoff/
Orchestra retrospectively extremely satisfied with symphony [No. 1] as
result of barrel of free beer.
-- Gustav Mahler, post-premiere letter to Arnold Berliner
next prev parent reply other threads:[~2014-03-11 5:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-08 6:13 [BUG?] ixgbe: only num_online_cpus() of the tx queues are enabled Ming Chen
2014-03-08 7:12 ` John Fastabend
2014-03-09 0:19 ` Ming Chen
2014-03-08 15:27 ` Eric Dumazet
2014-03-08 16:08 ` Eric Dumazet
2014-03-09 0:53 ` Ming Chen
2014-03-09 3:37 ` Eric Dumazet
2014-03-09 3:52 ` John Fastabend
2014-03-09 4:11 ` Eric Dumazet
2014-03-09 6:56 ` Ming Chen
2014-03-11 4:56 ` Geoff Kuenning [this message]
2014-03-09 6:47 ` Ming Chen
2014-03-09 13:39 ` Eric Dumazet
2014-03-09 22:31 ` David Miller
2014-03-09 0:30 ` Ming Chen
2014-03-09 3:29 ` Eric Dumazet
2014-03-09 6:43 ` Ming Chen
2014-03-09 13:44 ` Eric Dumazet
2014-03-09 19:22 ` Ming Chen
2014-03-09 19:37 ` Eric Dumazet
2014-03-09 19:41 ` Eric Dumazet
2014-03-09 19:43 ` Ming Chen
2014-03-10 5:40 ` Ming Chen
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=pnizjkxxri8.fsf@bow.cs.hmc.edu \
--to=geoff@cs.hmc.edu \
--cc=dhildeb@us.ibm.com \
--cc=eric.dumazet@gmail.com \
--cc=ezk@fsl.cs.sunysb.edu \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=v.mingchen@gmail.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).