netdev - Re: [RFC net-next 00/14] 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4FE2ADF8.8010508@broadcom.com>
Date:	Thu, 21 Jun 2012 08:15:36 +0300
From:	"Yuval Mintz" <yuvalmin@...adcom.com>
To:	"Ben Hutchings" <bhutchings@...arflare.com>
cc:	netdev@...r.kernel.org, davem@...emloft.net, eilong@...adcom.com,
	"Divy Le Ray" <divy@...lsio.com>,
	"Or Gerlitz" <ogerlitz@...lanox.com>,
	"Jon Mason" <jdmason@...zu.us>,
	"Anirban Chakraborty" <anirban.chakraborty@...gic.com>,
	"Jitendra Kalsaria" <jitendra.kalsaria@...gic.com>,
	"Ron Mercer" <ron.mercer@...gic.com>,
	"Jeff Kirsher" <jeffrey.t.kirsher@...el.com>,
	"Jon Mason" <mason@...i.com>,
	"Andrew Gallatin" <gallatin@...i.com>,
	"Sathya Perla" <sathya.perla@...lex.com>,
	"Subbu Seetharaman" <subbu.seetharaman@...lex.com>,
	"Ajit Khaparde" <ajit.khaparde@...lex.com>,
	"Matt Carlson" <mcarlson@...adcom.com>,
	"Michael Chan" <mchan@...adcom.com>
Subject: Re: [RFC net-next 00/14] default maximal number of RSS queues
 in mq drivers

On 06/20/2012 11:48 PM, Ben Hutchings wrote:

> Also, I would recommend encapsulating the calculation of default number
> of RSS queues in a function, rather than repeating it in every driver.
> That will make it easier to replace with something more sophisticated
> and configurable later on.
> 
> Ben.
> 

Do You also have the notion of where's the correct place to place such a
function?

Thanks,
Yuval

--
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