From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <damien.clabaut@corp.ovh.com> Received: from 2.mo302.mail-out.ovh.net (2.mo302.mail-out.ovh.net [137.74.110.75]) by dpdk.org (Postfix) with ESMTP id 8B5C51B27F for <dev@dpdk.org>; Thu, 12 Oct 2017 14:34:34 +0200 (CEST) Received: from EX2.OVH.local (gw1.corp.ovh.com [51.255.55.226]) by mo302.mail-out.ovh.net (Postfix) with ESMTPS id 504C52365D for <dev@dpdk.org>; Thu, 12 Oct 2017 14:34:34 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=corp.ovh.com; s=mailout; t=1507811674; bh=dzeSEPdYxpfEZWi338LJuJ5UtMJ0ZX3WjLUPDHqS9to=; h=Subject:CC:References:From:Date:In-Reply-To:From; b=CHfp9o3Enp1j7QMN7UxhgqyQMR8eJIaf0u5aEJ5AZRwXb2/f3dhQwMPdwWf8So4xr ICOs4Q7Nbr1QpEq8NT7eRak+zUkhrbj8PrVFk54qxQtOToO538bWPLPunRmIiIky3C BvIEt2OYb8UBQtuHtqN9Jn1RnTmR5idua+N/Qwb4= Received: from localhost.localdomain (149.56.136.2) by EX2.OVH.local (172.16.2.2) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1261.27; Thu, 12 Oct 2017 14:34:33 +0200 CC: "dev@dpdk.org" <dev@dpdk.org> References: <5f5aba8a-0dd2-fd64-891b-569d2a4627c8@corp.ovh.com> <B8E622BF-B147-4DB2-A24A-F8D8099CFB21@intel.com> <5cfff93d-213c-af2b-431f-437cd2eec6fc@corp.ovh.com> <D74C7355-B8EF-40F5-BC4C-E98E59215EF0@intel.com> <20171011185907.GA23268@yongseok-MBP.local> From: Damien Clabaut <damien.clabaut@corp.ovh.com> Message-ID: <46032f70-ca58-5076-51be-28d2918868dc@corp.ovh.com> Date: Thu, 12 Oct 2017 08:34:32 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <20171011185907.GA23268@yongseok-MBP.local> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Originating-IP: [149.56.136.2] X-ClientProxiedBy: EX3.OVH.local (172.16.2.3) To EX2.OVH.local (172.16.2.2) X-Ovh-Tracer-Id: 7014919370689115352 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 80 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedttddrtdeggdeftdcutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfqggfjpdevjffgvefmvefgnecuuegrihhlohhuthemuceftddtnecumhhishhsihhnghcuvffquchfihgvlhguucdlfedtmdenogetfeejfedqtdegucdlhedtmd Subject: Re: [dpdk-dev] Issue with pktgen-dpdk replaying >1500bytes pcap on MCX4 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Thu, 12 Oct 2017 12:34:34 -0000 Hello, I opened a ticket with Mellanox in parallel. We are trying to figure out why it doesn't work on MCX4 but it works on MCX3, even though MCX3 is not officially supported and neither are jumbo frames. In case you want to check, the case ID is 00392710. Regards, On 2017-10-11 02:59 PM, Yongseok Koh wrote: > On Thu, Sep 28, 2017 at 08:44:26PM +0000, Wiles, Keith wrote: >>> On Sep 26, 2017, at 8:09 AM, Damien Clabaut <damien.clabaut@corp.ovh.com> wrote: >>> >>> Hello Keith and thank you for your answer, >>> >>> The goal is indeed to generate as much traffic per machine as possible (we use pktgen-dpdk to benchmark datacenter routers before putting them on production). >>> >>> For this we use all available CPU power to send packets. >>> >>> Following your suggestion, I modified my command to: >>> >>> ./app/app/x86_64-native-linuxapp-gcc/pktgen -l 0-7 -- -m 1.0 -s 0:pcap/8500Bpp.pcap >> >> I just noticed you were sending 8500 byte frames and you have to modify Pktgen >> to increase the size of the mbufs in the mempool. I only configure the mbufs >> to 1518 byte buffers or really 2048 byte, but I only deal with 1518 max size. >> The size can be changed, but I am not next to a machine right now. > Hi Damien, > > Could you manage to resolve this issue? Keith mentioned pktgen doesn't support > jumbo frames w/o modifying code. Do you still have an issue with Mellanox NIC > and its PMDs? Please let me know. > > Thanks > Yongseok -- Damien Clabaut R&D vRouter ovh.qc.ca