netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: yuvalmin@broadcom.com
Cc: netdev@vger.kernel.org, eilong@broadcom.com, divy@chelsio.com,
	ogerlitz@mellanox.com, jdmason@kudzu.us,
	anirban.chakraborty@qlogic.com, jitendra.kalsaria@qlogic.com,
	ron.mercer@qlogic.com, jeffrey.t.kirsher@intel.com,
	mason@myri.com, gallatin@myri.com, sathya.perla@emulex.com,
	subbu.seetharaman@emulex.com, ajit.khaparde@emulex.com,
	mcarlson@broadcom.com, mchan@broadcom.com,
	eric.dumazet@gmail.com, bhutchings@solarflare.com
Subject: Re: [PATCH net-next 00/11] default maximal number of RSS queues in mq drivers
Date: Thu, 05 Jul 2012 03:07:38 -0700 (PDT)	[thread overview]
Message-ID: <20120705.030738.1582003570606539876.davem@davemloft.net> (raw)
In-Reply-To: <1341148740-7375-1-git-send-email-yuvalmin@broadcom.com>

From: "Yuval Mintz" <yuvalmin@broadcom.com>
Date: Sun, 1 Jul 2012 16:18:49 +0300

> Different vendors support different number of RSS queues by default. Today,
> there exists an ethtool API through which users can change the number of
> channels their driver supports; This enables us to pursue the goal of using
> a default number of RSS queues in various multi-queue drivers.
> 
> This patch intendeds to achieve the above default, by upper-limiting the number
> of interrupts multi-queue drivers request (by default, not via the new API) 
> with correlation to the number of cpus on the machine.

Applied to net-next, thanks a lot.

      parent reply	other threads:[~2012-07-05 10:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-01 13:18 [PATCH net-next 00/11] default maximal number of RSS queues in mq drivers Yuval Mintz
2012-07-01 13:18 ` [PATCH net-next 01/11] net-next: Add netif_get_num_default_rss_queues Yuval Mintz
2012-07-01 13:18 ` [PATCH net-next 02/11] mlx4: set maximal number of default RSS queues Yuval Mintz
2012-07-01 13:18 ` [PATCH net-next 03/11] vxge: " Yuval Mintz
2012-07-01 13:18 ` [PATCH net-next 04/11] qlge: " Yuval Mintz
2012-07-01 13:18 ` [PATCH net-next 05/11] cxgb3: " Yuval Mintz
2012-07-01 13:18 ` [PATCH net-next 06/11] cxgb4: " Yuval Mintz
2012-07-01 13:18 ` [PATCH net-next 07/11] myri10ge: " Yuval Mintz
2012-07-01 13:18 ` [PATCH net-next 08/11] tg3: " Yuval Mintz
2012-07-01 13:18 ` [PATCH net-next 09/11] bnx2: " Yuval Mintz
2012-07-01 13:18 ` [PATCH net-next 10/11] bnx2x: " Yuval Mintz
2012-07-01 13:19 ` [PATCH net-next 11/11] be2net: " Yuval Mintz
2012-07-01 15:01 ` [PATCH net-next 00/11] default maximal number of RSS queues in mq drivers Or Gerlitz
2012-07-02  4:55   ` Yuval Mintz
2012-07-05 10:07 ` David Miller [this message]

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=20120705.030738.1582003570606539876.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ajit.khaparde@emulex.com \
    --cc=anirban.chakraborty@qlogic.com \
    --cc=bhutchings@solarflare.com \
    --cc=divy@chelsio.com \
    --cc=eilong@broadcom.com \
    --cc=eric.dumazet@gmail.com \
    --cc=gallatin@myri.com \
    --cc=jdmason@kudzu.us \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jitendra.kalsaria@qlogic.com \
    --cc=mason@myri.com \
    --cc=mcarlson@broadcom.com \
    --cc=mchan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@mellanox.com \
    --cc=ron.mercer@qlogic.com \
    --cc=sathya.perla@emulex.com \
    --cc=subbu.seetharaman@emulex.com \
    --cc=yuvalmin@broadcom.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).