From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/4]: net: Allow RX queue selection to seed TX queue hashing.
Date: Wed, 28 Jan 2009 21:01:42 -0800 (PST) [thread overview]
Message-ID: <20090128.210142.06933232.davem@davemloft.net> (raw)
In-Reply-To: <20090129044148.GA25131@gondor.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Thu, 29 Jan 2009 15:41:48 +1100
> But yeah if a single TX queue isn't big enough to take care of
> the output from a single core then you will need multiple TX
> queues. Although from an system-wide point of view it would
> seem to be more optimal to make that TX queue bigger rather than
> forcing the software to use multiple queues (which may come with
> a bigger overhead) to make up for it.
>
> Of course for us software developers we don't really have a choice :)
Yes, this is one of the things I told Robert, make the
TX queues larger :-)
Besides, a plain iterating RX --> TX function can't work because
that doesn't take flows into consideration and thus can introduce
reordering.
next prev parent reply other threads:[~2009-01-29 5:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 0:40 [PATCH 1/4]: net: Allow RX queue selection to seed TX queue hashing David Miller
2009-01-28 8:53 ` Herbert Xu
2009-01-28 9:29 ` Eric Dumazet
2009-01-28 20:22 ` David Miller
2009-01-28 21:31 ` Herbert Xu
2009-01-29 0:40 ` David Miller
2009-01-29 1:34 ` Herbert Xu
2009-01-29 1:45 ` David Miller
2009-01-29 4:41 ` Herbert Xu
2009-01-29 5:01 ` David Miller [this message]
2009-01-28 18:50 ` Brandeburg, Jesse
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=20090128.210142.06933232.davem@davemloft.net \
--to=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).