netdev - Re: [PATCH net-next 00/11] default maximal number of RSS queues in mq drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20120705.030738.1582003570606539876.davem@davemloft.net>
Date:	Thu, 05 Jul 2012 03:07:38 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	yuvalmin@...adcom.com
Cc:	netdev@...r.kernel.org, eilong@...adcom.com, divy@...lsio.com,
	ogerlitz@...lanox.com, jdmason@...zu.us,
	anirban.chakraborty@...gic.com, jitendra.kalsaria@...gic.com,
	ron.mercer@...gic.com, jeffrey.t.kirsher@...el.com, mason@...i.com,
	gallatin@...i.com, sathya.perla@...lex.com,
	subbu.seetharaman@...lex.com, ajit.khaparde@...lex.com,
	mcarlson@...adcom.com, mchan@...adcom.com, eric.dumazet@...il.com,
	bhutchings@...arflare.com
Subject: Re: [PATCH net-next 00/11] default maximal number of RSS queues in
 mq drivers

From: "Yuval Mintz" <yuvalmin@...adcom.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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html