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 75A98A0548; Tue, 20 Apr 2021 12:15:44 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 42BA2412B0; Tue, 20 Apr 2021 12:15:44 +0200 (CEST) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by mails.dpdk.org (Postfix) with ESMTP id 77977411A5 for ; Tue, 20 Apr 2021 12:15:42 +0200 (CEST) IronPort-SDR: DzKj/QRNR+cyMVTsajkMsDytUz7PGLjLUP5S/31HA3P0Qlc/Sd9ZPfZhS1j9Fh3Pi5GmZQH8+B aI2yp810eFjg== X-IronPort-AV: E=McAfee;i="6200,9189,9959"; a="216068337" X-IronPort-AV: E=Sophos;i="5.82,236,1613462400"; d="scan'208";a="216068337" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Apr 2021 03:15:40 -0700 IronPort-SDR: kF2D/HViNbgm+c65m3F1z15IMQsCHmK0CLSUScJyPxUoZcHmy25PyaOLEO0ABlNVMpPrgBqkyZ aY/KxqNBO31w== X-IronPort-AV: E=Sophos;i="5.82,236,1613462400"; d="scan'208";a="420350140" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.213.207.27]) ([10.213.207.27]) by fmsmga008-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Apr 2021 03:15:39 -0700 To: Ciara Loftus , dev@dpdk.org References: <20210420084431.6417-1-ciara.loftus@intel.com> From: Ferruh Yigit X-User: ferruhy Message-ID: Date: Tue, 20 Apr 2021 11:15:35 +0100 MIME-Version: 1.0 In-Reply-To: <20210420084431.6417-1-ciara.loftus@intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH 1/2] net/af_xdp: fix trigger for syscall on tx X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list 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 4/20/2021 9:44 AM, Ciara Loftus wrote: > The send() syscall on the tx path is not concerned with busy polling > and as such its invocation should not depend on whether or not it is > configured. Fix this by distinguishing the conditions necessary for > syscalls on the rx and tx paths individually. > > Fixes: 055a393626ed ("net/af_xdp: prefer busy polling") > > Signed-off-by: Ciara Loftus Series applied to dpdk-next-net/main, thanks.