From mboxrd@z Thu Jan 1 00:00:00 1970 From: Remy Horton Subject: Re: [PATCH v2 4/4] testpmd: make use of per-PMD TxRx parameters Date: Tue, 3 Apr 2018 12:00:18 +0100 Message-ID: References: <20180321142749.27520-1-remy.horton@intel.com> <20180321142749.27520-5-remy.horton@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: John McNamara , Wenzhuo Lu , Jingjing Wu , Qi Zhang , Beilei Xing , Thomas Monjalon To: Shreyansh Jain , "dev@dpdk.org" Return-path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 1EE871B6BA for ; Tue, 3 Apr 2018 13:00:21 +0200 (CEST) In-Reply-To: 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 28/03/2018 08:18, Shreyansh Jain wrote: [..] > Can the change for burst size too be accommodated in this patch? I > looked through them and they might not be as trivial as the change > above - but if that is incorporated in this, it might serve as > example for other applications. Testpmd doesn't really distinguish between Rx and TX burst sizes, having just a single user-specifiable nb_pkt_per_burst parameter. However filling it with the preferred Rx burst size seems a good balance between providing a usage example and amount of code changes required.