From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH] doc: add known issue for virtio TSO with clones Date: Mon, 6 Feb 2017 15:10:47 -0800 Message-ID: <20170206151047.155aa0aa@xeon-e3> References: <1486387013-1706-1-git-send-email-olivier.matz@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org, yuanhan.liu@linux.intel.com, john.mcnamara@intel.com To: Olivier Matz Return-path: Received: from mail-pg0-f43.google.com (mail-pg0-f43.google.com [74.125.83.43]) by dpdk.org (Postfix) with ESMTP id EC26F293B for ; Tue, 7 Feb 2017 00:10:55 +0100 (CET) Received: by mail-pg0-f43.google.com with SMTP id 14so32323160pgg.1 for ; Mon, 06 Feb 2017 15:10:55 -0800 (PST) In-Reply-To: <1486387013-1706-1-git-send-email-olivier.matz@6wind.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Mon, 6 Feb 2017 14:16:53 +0100 Olivier Matz wrote: > +**Implication**: > + In this situation, the shared data will be modified by the driver, > + potentially causing race conditions with the other users of the mbuf > + data. This is a driver bug! The driver must check for refcount and not modify mbuf's whose refcnt > 1. For those mbuf's it should copy the mbuf and modify the copy. It is not good to force buggy refcnt handling back onto the application. It is acceptable to document the performance impact.