| 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
| ||
|
Message-Id: <20140117.190115.1213172764234203288.davem@davemloft.net> Date: Fri, 17 Jan 2014 19:01:15 -0800 (PST) From: David Miller <davem@...emloft.net> To: VenkatKumar.Duvvuru@...lex.Com Cc: netdev@...r.kernel.org Subject: Re: [PATCH 0/4] Patchset - Support for configurable RSS hash key From: Venkata Duvvuru <VenkatKumar.Duvvuru@...lex.Com> Date: Fri, 17 Jan 2014 13:02:10 +0000 > NIC drivers that support RSS use either a hard-coded value or a random value for the RSS hash key. Irrespective of the type of the key used, the user would want to change the hash key if he/she is not satisfied with the effectiveness of the default hash-key in spreading the incoming flows evenly across the RSS queues. > > This patch set provides support for configuring the RSS hash-key via the ethtool interface. > > The patch set consists of: > a) ethtool user-land patches > b) ethtool kernel patch > c) be2net patch that implements the ethtool hooks Your submission is confusing. Changes for the kernel side of things should be submitted as a separate series, and you do not need to mention where the tree was, via SHA ID, in the commit message. It is sufficient to say that your patches are against the 'net-net' tree, but after the "---" delimiter. It's not useful in the commit message proper. -- 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