From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [PATCH v9 1/8] ethdev: use locks to protect Rx/Tx
	callback lists
Date: Wed, 15 Jun 2016 15:49:17 +0200
Message-ID: <6135378.GQTxzoqr34@xps13>
References: <1465575534-23605-1-git-send-email-reshma.pattan@intel.com>
 <2907169.iIEIeOfXh7@xps13>
 <2601191342CEEE43887BDE71AB97725836B7164D@irsmsx105.ger.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: "Pattan, Reshma" <reshma.pattan@intel.com>, dev@dpdk.org
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-lf0-f52.google.com (mail-lf0-f52.google.com
 [209.85.215.52]) by dpdk.org (Postfix) with ESMTP id C13B4C5A8
 for <dev@dpdk.org>; Wed, 15 Jun 2016 15:49:19 +0200 (CEST)
Received: by mail-lf0-f52.google.com with SMTP id j7so13065626lfg.1
 for <dev@dpdk.org>; Wed, 15 Jun 2016 06:49:19 -0700 (PDT)
In-Reply-To: <2601191342CEEE43887BDE71AB97725836B7164D@irsmsx105.ger.corp.intel.com>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

I agree this patch do not bring a new issue.
But the current status deserves to be discussed.

2016-06-15 09:54, Ananyev, Konstantin:
> It is safe to add/remove RX/TX callbacks while 
> another thread is doing simultaneously RX/TX burst over same queue.

You are probably right, but I don't why it is safe? On which CPU?
How can we be sure that read and write of the "next" pointer are atomic?