netdev - Re: [RFC PATCH V2] New Xen netback implementation

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: <1327938597.26983.246.camel@zakaz.uk.xensource.com>
Date:	Mon, 30 Jan 2012 15:49:57 +0000
From:	Ian Campbell <Ian.Campbell@...rix.com>
To:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
CC:	"Wei Liu (Intern)" <wei.liu2@...rix.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
	David Vrabel <david.vrabel@...rix.com>,
	Paul Durrant <Paul.Durrant@...rix.com>
Subject: Re: [RFC PATCH V2] New Xen netback implementation

On Mon, 2012-01-30 at 15:21 +0000, Konrad Rzeszutek Wilk wrote:
> On Mon, Jan 30, 2012 at 03:07:16PM +0000, Ian Campbell wrote:
> > On Fri, 2012-01-27 at 19:22 +0000, Konrad Rzeszutek Wilk wrote:
> > > 
> > >  - This patch set solves the CPU banding problem I've seen with the
> > >    older netback. The older one  I could see X netback threads eating
> > > 80%
> > >    of CPU. With this one, the number is down to 13-14%. 
> > 
> > "CPU banding problem"?
> > 
> > If you had X threads using 80% before do you now see Y threads using
> > 13-14% where Y is bigger or smaller than X? Is 80*X ~= 13*Y?
> 
> Yes. ~=. The count looked to be the same.

Great, that's as expected, the same work is more fairly distributed -- I
thought you might be suggesting the total had gone down from
X*80%->X*13% which is not what I thought this series would be doing!

Ian.

--
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