From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <msvmohanraj@gmail.com>
Received: from mail-wm0-f41.google.com (mail-wm0-f41.google.com [74.125.82.41])
 by dpdk.org (Postfix) with ESMTP id 22BEB1B336
 for <dev@dpdk.org>; Mon,  5 Feb 2018 14:30:28 +0100 (CET)
Received: by mail-wm0-f41.google.com with SMTP id v71so25931510wmv.2
 for <dev@dpdk.org>; Mon, 05 Feb 2018 05:30:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=mime-version:from:date:message-id:subject:to;
 bh=b8GEWkn8rJk2JTY9Zgmqu1EWm+3K24v8K4hOZQ3PA2g=;
 b=Hz0QdKJ0p/r3uIZ3pz2YBvoDywoBeMzvQYvUqyjxek9KbWE57wXgXpCWFvRCRJQyRx
 C20Zy4kYlhtfi0IkK8AfvxeHVgtCxnEvJpDM1KEuymaSv1Q9as76N6hxixL2sctZL6cm
 HNouYPlHyZPiooSY5A8cvbQnET4ou7Q0ket+gIT+vlU955LWaOE8p9cli50S0OHmap4W
 geToC6/5WeLLAg9e5j/1HVP6BTbhwUACsRXGObN42RvQ3bN/Al8Y0DMsJce77ylFauAr
 Dy93N0pziurEqgsIVfeLNs0ku5bJnCLvmTrEegqJR1QpeWcdmq6oRZglFSnEjRHl/N1Q
 uqaw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
 bh=b8GEWkn8rJk2JTY9Zgmqu1EWm+3K24v8K4hOZQ3PA2g=;
 b=M96lT+HtWXoqjUjaTcSKEstsONCx1GT7qpm1TZMBYp2de+wGLP42QuNnKtZCe28S7b
 MCsHbkOzsyCSsi22wmMLQkjyi7aDO80nnprfVcHdY9ij8d57p4ge2lcme3V7Yhn3e8lV
 wnL0IQfhRqAEYV2c7BUCj3RuFOo9nwv1FZ61fkjpTxgiFMJpoAyaztdqIJTdRN7WgUMt
 SLZP3Mp0xOSQgfX6AWfV3wrn1iupBBIZUqe8MBXgtmpJ5tvrPWP5PLXOZb4ZW1nwMEyC
 37CG5MBJp8gNU/x7yyqobBapUHfsd7457Ut7TkuDQn/t7+rnCn4P5r2ixMCW+jbtP11T
 AlRA==
X-Gm-Message-State: APf1xPCRqS5OfQyQixMo8Nn5aEVwpG6dryHTkJLJ1gAnxdeSjpm6hXrN
 8uzqgexR9JgEfT0g4jzlCQRJIAZ44HevlrJwyTY=
X-Google-Smtp-Source: AH8x227qnIduTvBz0fPJCYVHFl7idwZDj0VO+4BQDlAWuCy8xWtnYJdJUgQak5Klp4LkAxgfLdDNdLDj32o48mjzCsc=
X-Received: by 10.28.120.19 with SMTP id t19mr3964743wmc.53.1517837427400;
 Mon, 05 Feb 2018 05:30:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.164.73 with HTTP; Mon, 5 Feb 2018 05:30:27 -0800 (PST)
From: Mohanraj Venkat <msvmohanraj@gmail.com>
Date: Mon, 5 Feb 2018 19:00:27 +0530
Message-ID: <CAH9UErXA6S=sH50_AzzRr1UBVw_NB=RQ-s2U+Gbt70O0k1Kv1w@mail.gmail.com>
To: dev@dpdk.org
Content-Type: text/plain; charset="UTF-8"
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-dev] Crash during rte_acl_classify while other core is
 building the filter context using rte_acl_build()
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://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: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Feb 2018 13:30:28 -0000

Hi,

How to resolve the following crash without using lock in dpdk ?


Crash occurs while a core is doing rte_acl_classify() for a packet when
other core is trying to build the same filter context using rte_acl_build().

How to resolve this issue without using lock as lock affects the
performance ? or Is there any other way using lock which will not affect
the performance. ?



Thanks,
Mohanraj V