netdev - Re: [PATCH net-next V3 1/3] xen-netback: split event channels support for Xen backend driver

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] [day] [month] [year] [list]

Message-ID: <20130624101807.GA2394@zion.uk.xensource.com>
Date:	Mon, 24 Jun 2013 11:18:07 +0100
From:	Wei Liu <wei.liu2@...rix.com>
To:	Jan Beulich <JBeulich@...e.com>
CC:	Wei Liu <wei.liu2@...rix.com>, <david.vrabel@...rix.com>,
	<ian.campbell@...rix.com>, <xen-devel@...ts.xen.org>,
	<annie.li@...cle.com>, <konrad.wilk@...cle.com>,
	<netdev@...r.kernel.org>
Subject: Re: [PATCH net-next V3 1/3] xen-netback: split event channels
 support for Xen backend driver

On Mon, Jun 24, 2013 at 10:48:25AM +0100, Jan Beulich wrote:
> >>> On 22.05.13 at 18:34, Wei Liu <wei.liu2@...rix.com> wrote:
> > Netback and netfront only use one event channel to do TX / RX notification,
> > which may cause unnecessary wake-up of processing routines. This patch adds a
> > new feature called feature-split-event-channels to netback, enabling it to
> > handle TX and RX events separately.
> > 
> > Netback will use tx_irq to notify guest for TX completion, rx_irq for RX
> > notification.
> 
> While I can see the benefit for the frontend, does this really make
> a lot of a difference to the backend considering that both rx and tx
> handling get done on the same thread anyway?
> 

Not for now. But I'm working on separating the backend handling routines.

So if you're thinking about backporting, I don't think this is the
material.


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