From: David Miller <davem@davemloft.net>
To: andy.grover@gmail.com
Cc: herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: using huge numbers of queues
Date: Wed, 07 Oct 2009 15:38:11 -0700 (PDT) [thread overview]
Message-ID: <20091007.153811.139592035.davem@davemloft.net> (raw)
In-Reply-To: <c0a09e5c0910071459r2768f420lae87f7404dfbc054@mail.gmail.com>
From: Andrew Grover <andy.grover@gmail.com>
Date: Wed, 7 Oct 2009 14:59:49 -0700
> At NetConf, you made a passing remark about wanting lots of queues,
> even 1-per-socket. Have you thought further about how we would use so
> many?
Classification.
Lots and lots of virtual queues, which map to a smaller number
of physical queues for delivery.
The virtual queue matched serves as a index and a classification
hint to things like GRO receive, etc.
next prev parent reply other threads:[~2009-10-07 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 21:59 using huge numbers of queues Andrew Grover
2009-10-07 22:38 ` David Miller [this message]
2009-10-08 19:56 ` Mark Smith
2009-10-07 23:22 ` Ben Hutchings
2009-10-09 1:02 ` Herbert Xu
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=20091007.153811.139592035.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy.grover@gmail.com \
--cc=herbert@gondor.apana.org.au \
--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).