Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757877Ab0KKI3E (ORCPT ); Thu, 11 Nov 2010 03:29:04 -0500 Received: from mga09.intel.com ([134.134.136.24]:52740 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757825Ab0KKI3B convert rfc822-to-8bit (ORCPT ); Thu, 11 Nov 2010 03:29:01 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.59,181,1288594800"; d="scan'208";a="572461895" From: "Xin, Xiaohui" To: David Miller CC: "netdev@vger.kernel.org" , "kvm@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "mst@redhat.com" , "mingo@elte.hu" , "herbert@gondor.apana.org.au" , "jdike@linux.intel.com" Date: Thu, 11 Nov 2010 16:28:21 +0800 Subject: RE: [PATCH v15 00/17] Provide a zero-copy method on KVM virtio-net. Thread-Topic: [PATCH v15 00/17] Provide a zero-copy method on KVM virtio-net. Thread-Index: AcuA/zEeWFozSaN8TTKcARQP14d4JQAeNB1w Message-ID: References: <20101109.091516.112581012.davem@davemloft.net> <1289381008-5484-1-git-send-email-xiaohui.xin@intel.com> <20101110.094641.193701683.davem@davemloft.net> In-Reply-To: <20101110.094641.193701683.davem@davemloft.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1541 Lines: 36 >-----Original Message----- >From: David Miller [mailto:davem@davemloft.net] >Sent: Thursday, November 11, 2010 1:47 AM >To: Xin, Xiaohui >Cc: netdev@vger.kernel.org; kvm@vger.kernel.org; linux-kernel@vger.kernel.org; >mst@redhat.com; mingo@elte.hu; herbert@gondor.apana.org.au; jdike@linux.intel.com >Subject: Re: [PATCH v15 00/17] Provide a zero-copy method on KVM virtio-net. > >From: xiaohui.xin@intel.com >Date: Wed, 10 Nov 2010 17:23:28 +0800 > >> From: Xin Xiaohui >> >>>2) The idea to key off of skb->dev in skb_release_data() is >>> fundamentally flawed since many actions can change skb->dev on you, >>> which will end up causing a leak of your external data areas. >> >> How about this one? If the destructor_arg is not a good candidate, >> then I have to add an apparent field in shinfo. > >If destructor_arg is actually a net_device pointer or similar, >you will need to take a reference count on it or similar. > Do you mean destructor_arg will be consumed by other user? If that case, may I add a new structure member in shinfo? Thus only zero-copy will use it, and no need for the reference count. >Which means --> good bye performance especially on SMP. > >You're going to be adding new serialization points and at >least two new atomics per packet. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/