From mboxrd@z Thu Jan 1 00:00:00 1970 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) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Apr 2018 04:00:21 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,400,1517904000"; d="scan'208";a="30640949" Received: from rhorton-mobl1.ger.corp.intel.com (HELO [163.33.230.27]) ([163.33.230.27]) by orsmga008.jf.intel.com with ESMTP; 03 Apr 2018 04:00:19 -0700 To: Shreyansh Jain , "dev@dpdk.org" References: <20180321142749.27520-1-remy.horton@intel.com> <20180321142749.27520-5-remy.horton@intel.com> Cc: John McNamara , Wenzhuo Lu , Jingjing Wu , Qi Zhang , Beilei Xing , Thomas Monjalon From: Remy Horton Organization: Intel Shannon Limited Message-ID: Date: Tue, 3 Apr 2018 12:00:18 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v2 4/4] testpmd: make use of per-PMD TxRx parameters X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Apr 2018 11:00:22 -0000 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.