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: Tue, 14 Jun 2016 21:59:55 +0200
Message-ID: <12886124.K2biJ8F8kE@xps13>
References: <1465575534-23605-1-git-send-email-reshma.pattan@intel.com>
 <1465897108-26548-1-git-send-email-reshma.pattan@intel.com>
 <1465897108-26548-2-git-send-email-reshma.pattan@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: dev@dpdk.org
To: Reshma Pattan <reshma.pattan@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wm0-f46.google.com (mail-wm0-f46.google.com [74.125.82.46])
 by dpdk.org (Postfix) with ESMTP id 9FF1AADBF
 for <dev@dpdk.org>; Tue, 14 Jun 2016 21:59:57 +0200 (CEST)
Received: by mail-wm0-f46.google.com with SMTP id k204so6078776wmk.0
 for <dev@dpdk.org>; Tue, 14 Jun 2016 12:59:57 -0700 (PDT)
In-Reply-To: <1465897108-26548-2-git-send-email-reshma.pattan@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>

2016-06-14 10:38, Reshma Pattan:
> Added spinlocks around add/remove logic of Rx and Tx callbacks
> to avoid corruption of callback lists in multithreaded context.
> 
> Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>

Why cb->next is not locked in burst functions?
Just protecting add/remove but not its usage seems useless.