[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20141116.160339.237379782878143946.davem@davemloft.net>
Date: Sun, 16 Nov 2014 16:03:39 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: edumazet@...gle.com
Cc: netdev@...r.kernel.org, Thomas.Lendacky@....com,
ariel.elior@...gic.com, mchan@...adcom.com, prashant@...adcom.com,
rasesh.mody@...gic.com, sathya.perla@...lex.com,
subbu.seetharaman@...lex.com, ajit.khaparde@...lex.com,
jesse.brandeburg@...el.com, jeffrey.t.kirsher@...el.com,
amirv@...lanox.com, sshah@...arflare.com, sbhatewara@...are.com
Subject: Re: [PATCH net-next 00/14] net: provide common RSS key
infrastructure
From: Eric Dumazet <edumazet@...gle.com>
Date: Sun, 16 Nov 2014 06:23:04 -0800
> RSS (Receive Side Scaling) uses a 40 bytes key to provide hash for incoming
> packets to select appropriate incoming queue on NIC.
>
> Hash algo (Toeplitz) is also well known and documented by Microsoft
> (search for "Verifying the RSS Hash Calculation")
>
> Problem is that some drivers use a well known key.
> It makes very easy for attackers to target one particular RX queue,
> knowing that number of RX queues is a power of two, or at least some
> small number.
>
> Other drivers use a random value per port, making difficult
> tuning on bonding setups.
>
> Lets add a common infrastructure, so that host gets an unique
> RSS key, and drivers do not have to worry about this.
Looks good, series applied, thanks Eric.
--
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