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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A0217F6.7060005@netxen.com>
Date:	Wed, 6 May 2009 16:06:30 -0700
From:	Dhananjay Phadke <dhananjay@...xen.com>
To:	David Miller <davem@...emloft.net>
CC:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [patch next 4/4] netxen: disable rss for GbE ports

The reason for RSS was to distribute the ingress traffic
to different CPUs. At 10Gbps, without RSS, one CPU was
saturating, acting as bottleneck. I can do 1Gbps with
only one CPU only 50% saturated, this to on a low end
server.

The fallout is more msix vectors being consumed for RSS,
when they don't really bring any performance gain.

Since NetXen has single driver, unlike others, it needs
to be dealt based on NIC board type.

-Dhananjay

David Miller wrote:
> From: Dhananjay Phadke <dhananjay@...xen.com>
> Date: Tue,  5 May 2009 22:05:09 -0700
> 
>> There's no advantage of receive side scaling on GbE ports, so
>> restrict rss support to 10GbE ports.
>>
>> Signed-off-by: Dhananjay Phadke <dhananjay@...xen.com>
> 
> This is your opinion.  And even if it is more than opinion,
> you give zero technical arguments in your commit message so
> we can see why this should be done.
> 
> Tell that opinion to the person with 10 netxen cards in their
> machine running at full tilt.
> 
> Tell that opinion to the person with extremely complicated and
> cpu intensive netfilter and routing rules in use.
> 
> I'm not applying this patch.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ