From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 113BBC433E0 for ; Fri, 29 Jan 2021 16:52:00 +0000 (UTC) Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by mail.kernel.org (Postfix) with ESMTP id 9614164DEB for ; Fri, 29 Jan 2021 16:51:59 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 9614164DEB Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7A16D240101; Fri, 29 Jan 2021 17:51:58 +0100 (CET) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by mails.dpdk.org (Postfix) with ESMTP id E668F40696; Fri, 29 Jan 2021 17:51:56 +0100 (CET) IronPort-SDR: z0q9vaZuEhiZwDICCGzLiOLMZ+hzPdcwmG5BgwnPe/CuNPFjpJSjUSCRaElisjNMcwt6cNBpam 4Pi+3lePhMkw== X-IronPort-AV: E=McAfee;i="6000,8403,9879"; a="180524434" X-IronPort-AV: E=Sophos;i="5.79,386,1602572400"; d="scan'208";a="180524434" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jan 2021 08:51:55 -0800 IronPort-SDR: Oq5tr0O+9+iw5ROc9xH2Mzv2basSwCChcb00XAvddlfuh+pe+V2GO3bD9R676tUAQQU8iBzu+I qkYdK6CGGXHA== X-IronPort-AV: E=Sophos;i="5.79,386,1602572400"; d="scan'208";a="389372570" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.213.197.204]) ([10.213.197.204]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jan 2021 08:51:51 -0800 To: Viacheslav Ovsiienko , dev@dpdk.org Cc: thomas@monjalon.net, beilei.xing@intel.com, bernard.iremonger@intel.com, wenzhuo.lu@intel.com, stable@dpdk.org References: <1611233193-20886-1-git-send-email-viacheslavo@nvidia.com> From: Ferruh Yigit Message-ID: <0f72ad8b-07b8-9cfb-f8d4-c7be1bfb24f3@intel.com> Date: Fri, 29 Jan 2021 16:51:48 +0000 MIME-Version: 1.0 In-Reply-To: <1611233193-20886-1-git-send-email-viacheslavo@nvidia.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH] app/testpmd: fix queue reconfig request on Rx split update 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 1/21/2021 12:46 PM, Viacheslav Ovsiienko wrote: > There is the "set rxpkts" command in the testpmd interactive mode, > it configures the segment sizes to split the packet on receiving. > The mentioned segment sizes are provided on the Rx queue setup > as part of queue configuration. Hence, to take the rxpkts command > into effect the Rx queues must be explicitly reconfigured. > > The explained above is related to the "set rxoffs" as well. > > The patch sets the queue reconfiguration request flag for > all devices once Rx split settings are updated, to take > the changes into effect the port(s) should be restarted. > > Fixes: 0f2096d7ab36 ("app/testpmd: add rxpkts commands and parameters") > Fixes: 91c78e090eed ("app/testpmd: add rxoffs commands and parameters") > Cc: stable@dpdk.org > > Signed-off-by: Viacheslav Ovsiienko Reviewed-by: Ferruh Yigit Applied to dpdk-next-net/main, thanks.