[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87wq6uiass.fsf@tassilo.jf.intel.com>
Date: Sun, 16 Nov 2014 22:46:43 -0800
From: Andi Kleen <andi@...stfloor.org>
To: Eric Dumazet <edumazet@...gle.com>
Cc: "David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org,
Thomas Lendacky <Thomas.Lendacky@....com>,
Ariel Elior <ariel.elior@...gic.com>,
Michael Chan <mchan@...adcom.com>,
Prashant Sreedharan <prashant@...adcom.com>,
Rasesh Mody <rasesh.mody@...gic.com>,
Sathya Perla <sathya.perla@...lex.com>,
Subbu Seetharaman <subbu.seetharaman@...lex.com>,
Ajit Khaparde <ajit.khaparde@...lex.com>,
Jesse Brandeburg <jesse.brandeburg@...el.com>,
Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
Amir Vadai <amirv@...lanox.com>,
Shradha Shah <sshah@...arflare.com>,
Shreyas Bhatewara <sbhatewara@...are.com>
Subject: Re: [PATCH net-next 01/14] net: provide a per host RSS key generic infrastructure
Eric Dumazet <edumazet@...gle.com> writes:
> Some drivers use a constant (and well known key), some drivers use a random
> key per port, making bonding setups hard to tune. Well known keys increase
> attack surface, considering that number of queues is usually a power of two.
Wouldn't it be better to have some kernel facility to query on what
port a given mapping would end up rather than exporting
the key? Similar to querying the rounting table.
That would be more abstract.
> + {
> + .procname = "netdev_rss_key",
> + .data = &netdev_rss_key,
> + .maxlen = sizeof(int),
> + .mode = 0444,
Surely 0400 ? After all it's a kind a "secret"
-Andi
--
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