From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 658B0A0C41 for ; Thu, 4 Nov 2021 15:09:55 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5CFAB42719; Thu, 4 Nov 2021 15:09:55 +0100 (CET) Received: from mail-yb1-f176.google.com (mail-yb1-f176.google.com [209.85.219.176]) by mails.dpdk.org (Postfix) with ESMTP id A05204003E for ; Tue, 26 Oct 2021 05:48:08 +0200 (CEST) Received: by mail-yb1-f176.google.com with SMTP id y80so13376227ybe.12 for ; Mon, 25 Oct 2021 20:48:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=mEIu3WrLkTbvFrnnQ+O4oivvF1Z0Zvv/oTWTKb1tNR8=; b=IAtqIxoB+K8c1KfgFuI5g+h2HBH73WUpUgSQG0CxEh4xG259OOwIfwBMppb+0wMfYu QhiPvdvkVWNsbDywVQP01rrLnMw32ovK/IhBV5Mx7DLToTMOFwCjn28g5fD/K6hVda7f V5MdctZD5DobujFVC+n7LF4vHRwiZ4mDmUKIb63v7XUX2wNCWnIjkWbCldBvIs5NHJ0o hbhcE7nkPPRKANjr7W0q4aFKZloTTuEQe+mvUAECkNj3oin0tBC+n6F/qak7V8An6BF1 sUPzfQ1Uw1mPkscMQHqPNdUU5aU5oJEwIPbDIKQuZ70c62eTaAMDrsmGfqZbSB33F1w1 0+rw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=mEIu3WrLkTbvFrnnQ+O4oivvF1Z0Zvv/oTWTKb1tNR8=; b=aR2k+nHhtFsvYaqFZeRzvVRBmZrlbE3PulxdqyvMgBp3Fxa+80vN78lsgK930HbiRk 371AxJOLSrf2WZclxL2oKv3P7+gZMIgIaHypeMOQjqaILK59WQrq5ExuTCzGEopegs6u dz/7wPcrEqRsgsTtR+oDdxGBs446hWWWAs2u2UPGALoetByUZ8NsfhCWoHi2Q1RFutFA ykiDfe5T0bjiP0R7dqIINXSN6sAaV2U5rZXHvTvmbxR9VoCqL6CTpmxOkgYj12IKjU2J 1omzekJTDThGcPxbqXOOAFFkQge/L3s7bVOUDeiqHLVWIJK01y1aopGIC2yQW63TN5FI J0Dw== X-Gm-Message-State: AOAM532QTXObHS1OZNKuDl0+O0hczgJJvXUteqgUmO8GpT0P9oabUmJF hc9NnVuTZEAJMmKld8tycK/RQxDvSEujMdbgx6GR+ByyX3c= X-Google-Smtp-Source: ABdhPJxWAf9RIDj8EF1Km7TxkWfj8pNePmCJjp14wo5lJnAZtSd6ubOwCgNkYKc97Kok0TmBzQkCz2MPkYVPtAYpLDI= X-Received: by 2002:a05:6902:683:: with SMTP id i3mr6484342ybt.388.1635220087930; Mon, 25 Oct 2021 20:48:07 -0700 (PDT) MIME-Version: 1.0 From: =?UTF-8?B?6Zmz5YGl5paw?= Date: Tue, 26 Oct 2021 11:47:57 +0800 Message-ID: Subject: Are KNI RX/TX burst API thread safe? To: users@dpdk.org Content-Type: multipart/alternative; boundary="00000000000078825105cf395889" X-Mailman-Approved-At: Thu, 04 Nov 2021 15:09:53 +0100 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --00000000000078825105cf395889 Content-Type: text/plain; charset="UTF-8" Hi all, Are these two functions rte_kni_tx_burst and rte_kni_rx_burst thread safe? Is that fine that I rx / tx the KNI with multiple lcore? Is there protection against access from multiple lcore? Do I need to use a lock to protect it? The DPDK I am using is 17.05.2 thanks, James --00000000000078825105cf395889 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

Are these two functions rte_kni= _tx_burst and=C2=A0rte_kni_rx_burst thread safe?
Is that fine tha= t I rx / tx the KNI with multiple lcore?
Is there protection agai= nst access from multiple=C2=A0lcore? Do=C2=A0I need to use a lock to protec= t it?

The DPDK I am using is 17.05.2
thanks,
James
--00000000000078825105cf395889--