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
| ||
|
Date: Sun, 18 Apr 2010 23:29:39 -0700 (PDT) From: David Miller <davem@...emloft.net> To: eilong@...adcom.com Cc: vladz@...adcom.com, netdev@...r.kernel.org, dmitry@...adcom.com Subject: Re: [PATCH 10/13] bnx2x: Set default value of num_queues to 1 on 32-bit platforms From: "Eilon Greenstein" <eilong@...adcom.com> Date: Mon, 19 Apr 2010 09:06:21 +0300 > Yes - running low on vmalloc is the reason. This patch does not restrict > the usage of multi queue on 32bits - it is just changing the default > queues values from the number of available CPUs to 1. If the user will > use another value, it will work as before. Changing the default to 1 is equivalent to disabling multi-queue. > We encounter few issues were a 32bit kernel was installed on a > multi-core platform and the driver allocated "too many" queues. One way > to go is to limit the queue size and the other is the number of queues - > leaving it as is caused issues due to running low on kernel virtual > memory so a change was needed. Look into using an allocation strategy other than vmalloc(), in fact I can't see why you need to much memory that vmalloc() must be used in the first place. -- 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
Powered by blists - more mailing lists