From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shirley Ma Subject: Re: [PATCH V5 2/6 net-next] netdevice.h: Add zero-copy flag in netdevice Date: Tue, 17 May 2011 13:53:19 -0700 Message-ID: <1305665599.10756.36.camel@localhost.localdomain> References: <1305574128.3456.23.camel@localhost.localdomain> <1305574518.2885.25.camel@bwh-desktop> <1305574680.3456.33.camel@localhost.localdomain> <1305575253.2885.28.camel@bwh-desktop> <20110516211459.GE18148@redhat.com> <1305588738.3456.65.camel@localhost.localdomain> <20110517062111.GD26989@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Ben Hutchings , David Miller , Eric Dumazet , Avi Kivity , Arnd Bergmann , netdev@vger.kernel.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org To: "Michael S. Tsirkin" Return-path: In-Reply-To: <20110517062111.GD26989@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Tue, 2011-05-17 at 09:21 +0300, Michael S. Tsirkin wrote: > Problem is, in your patch there are a set of restrictions on what the > device can do with the skb that we need to enforce somehow. > Also, how do we know it's a 'real NIC' and not a software device? I checked macvtap newlink, it doesn't seem to block software device. So we need to work on the wider feature bit first. Shirley