Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Tom Herbert <therbert@google.com>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
	davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH] xps-mq: Transmit Packet Steering for multiqueue
Date: Wed, 01 Sep 2010 17:54:23 +0200	[thread overview]
Message-ID: <1283356463.2556.351.camel@edumazet-laptop> (raw)
In-Reply-To: <AANLkTin2rmcsxHi6+bFEUykhrkoWs--hrisAx_v__k1D@mail.gmail.com>

Le mercredi 01 septembre 2010 à 08:41 -0700, Tom Herbert a écrit :
> > Why don't we do this in the normal transmit processing.
> > There is already so much policy mechanism filters/actions/qdisc that
> > doing it in higher level is fighting against these.
> >
> Are you proposing that TX queue selection be done in the qdiscs?  The
> queue has to be selected before taking the lock (cannot afford taking
> a lock over the whole interface).  This would necessitate moving the
> locking and probably rearranging a lot of the xmit code around that.

Stephen point is not adding yet another layer 'before' qdisc layer.

I would like something not as complex as your patch.

1) Why current selection fails ?

2) Could we change current selection to :

 - Use a lightweight selection, with no special configuration.

 - Use driver RX multiqueue information if available, in a one-to-one
relationship.

3) Eventually have a user selectable selection (socket option, or system
wide, but one sysctl, not many bitmasks ;) ).




  reply	other threads:[~2010-09-01 15:54 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-23  5:39 [PATCH] xps-mq: Transmit Packet Steering for multiqueue Tom Herbert
2010-08-23 17:09 ` Ben Hutchings
     [not found]   ` <AANLkTinST5zaS0NtBjrzyLbsg=w_EVsHE3DCDcrmQNc6@mail.gmail.com>
2010-08-23 17:50     ` Ben Hutchings
2010-08-23 17:59 ` Stephen Hemminger
2010-09-01 15:41   ` Tom Herbert
2010-09-01 15:54     ` Eric Dumazet [this message]
2010-09-01 16:24       ` Tom Herbert
2010-09-02  1:32         ` David Miller
2010-09-02  1:48           ` Stephen Hemminger
2010-09-02 16:00             ` Loke, Chetan
2010-09-02 19:52               ` Tom Herbert
2010-09-02 23:17                 ` Loke, Chetan
2010-09-02  1:56           ` Stephen Hemminger
2010-09-02  6:41             ` Greg Lindahl
2010-09-02 16:18             ` Loke, Chetan
2010-09-02 15:55           ` Loke, Chetan
2010-09-16 21:52           ` Ben Hutchings
2010-09-19 17:24             ` Michael S. Tsirkin
2010-09-20 12:44               ` [RFC][PATCH 1/3] IRQ: Add irq_get_numa_node() Ben Hutchings
2010-09-20 13:04                 ` Eric Dumazet
2010-09-20 12:45               ` [RFC][PATCH 2/3] ethtool: NUMA affinity control Ben Hutchings
2010-09-20 12:48               ` [RFC][PATCH 3/3] sfc: Add support for " Ben Hutchings
2011-02-21 18:19           ` [PATCH] xps-mq: Transmit Packet Steering for multiqueue Ben Hutchings
2011-02-21 19:31             ` Jeremy Eder
2011-02-26  7:09             ` David Miller
2010-09-01 16:09     ` David Miller
2010-08-24  4:31 ` Bill Fink
2010-08-24  4:37   ` Tom Herbert

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=1283356463.2556.351.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    --cc=therbert@google.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