From: Mark Smith <lk-netdev@lk-netdev.nosense.org>
To: David Miller <davem@davemloft.net>
Cc: andy.grover@gmail.com, herbert@gondor.apana.org.au,
netdev@vger.kernel.org
Subject: Re: using huge numbers of queues
Date: Fri, 9 Oct 2009 06:26:38 +1030 [thread overview]
Message-ID: <20091009062638.1cd54c64@opy.nosense.org> (raw)
In-Reply-To: <20091007.153811.139592035.davem@davemloft.net>
On Wed, 07 Oct 2009 15:38:11 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> 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.
Is that similar to what is described in
Trading Packet Headers for Packet Processing
http://www.sigcomm.org/sigcomm95/papers/chandranmenon.ps
?
My understanding of that paper is that when a packet enters the host it
is classified using various attributes e.g. Ip src/dest/etc, and then
assigned an unique identifier. Subsequent processing of the packet is
indexed by this identifier, rather than each processing stage
performing it's own packet classification and selection.
For packets that are forwarded, the packet is then tagged/labled with
an ID, so that subsequent hosts don't have to perform classification
either.
(This paper is pretty much the origins of MPLS, which is where my
original interest came from)
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-08 19:57 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
2009-10-08 19:56 ` Mark Smith [this message]
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=20091009062638.1cd54c64@opy.nosense.org \
--to=lk-netdev@lk-netdev.nosense.org \
--cc=andy.grover@gmail.com \
--cc=davem@davemloft.net \
--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).