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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 23 Oct 2009 06:45:52 +0900
From:	Stephen Hemminger <shemminger@...tta.com>
To:	David Miller <davem@...emloft.net>
Cc:	peter.p.waskiewicz.jr@...el.com, jeffrey.t.kirsher@...el.com,
	gospo@...hat.com, netdev@...r.kernel.org
Subject: Re: [net-next-2.6 PATCH 2/3] ixgbe: Set MSI-X vectors to
 NOBALANCING and set affinity

On Thu, 22 Oct 2009 03:56:01 -0700 (PDT)
David Miller <davem@...emloft.net> wrote:

> From: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@...el.com>
> Date: Thu, 22 Oct 2009 01:22:36 -0700
> 
> > The first thing any performance guide says is to disable irqbalance
> 
> Such guides are wrong, and that's the end of this discussion.
> 
> These kinds of guides also say to do all kinds of crazy things with
> the socket sysctl settings.  That's wrong too and we absolutely do not
> do things to accomodate nor support those guide suggestions.
> 
> And we won't do that here.
> 
> I'm especially not going to succumb in this case because Arjan has
> been more than responsive to making sure irqbalanced in userspace does
> the right thing for networking devices, even multiqueue ones.
> 
> So we can make it do the right thing when flow director is present.
> In fact, the thing you want for flow director makes sense in the
> general case too.

irqbalance daemon already has IRQBALANCE_BANNED_INTERRUPTS
to work around this. It also has code to special case devices, if you
think ixgbe needs special treatment, why not do it there.
--
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