netdev - Re: [net-next patch 8/12] bnx2x: Allow up to 63 RSS queues default 8 queues

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 for Android: free password hash cracker in your pocket

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

Date:	Sun, 17 Jun 2012 12:31:28 +0300
From:	"Eilon Greenstein" <eilong@...adcom.com>
To:	"David Miller" <davem@...emloft.net>
cc:	meravs@...adcom.com, eric.dumazet@...il.com, netdev@...r.kernel.org
Subject: Re: [net-next patch 8/12] bnx2x: Allow up to 63 RSS queues
 default 8 queues

On Sun, 2012-06-17 at 02:00 -0700, David Miller wrote:
> From: "Eilon Greenstein" <eilong@...adcom.com>
> Date: Sun, 17 Jun 2012 11:33:56 +0300
> 
> > drivers now, it does not sound like a good path - so I was asking if you
> > can consider a kernel parameter as acceptable path. To be clear, I'm
> > asking if adding the default for all multi-queue drivers in the form of
> > a kernel parameter is a good path to explore.
> 
> If it's the default, there's no need for a kernel command line
> parameter.  Those suck, just pick a good default.
> 

OK. So we will send an RFC series setting the default (hard coded
define) to 8 for all multi-queue drivers and that will start a
discussion if this is a good default number or not. The side-effect of
this series will be that drivers that did not implement set_channels
will not be able to change this default back to the HW limit like they
run today (assuming the HW limit is higher than the chosen default).

On top of that, we will send this series for the bnx2x again without any
default -allowing up to 64 queues unless set_channels is used.

Eilon

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