From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from delivery.mailspamprotection.com (delivery.mailspamprotection.com [108.163.201.229]) by dpdk.org (Postfix) with ESMTP id 820DE1B471 for ; Fri, 15 Feb 2019 06:59:51 +0100 (CET) Received: from ns1.es18.siteground.eu ([37.60.250.193] helo=es18.siteground.eu) by se2.mailspamprotection.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1guWXK-000AOA-Q9; Thu, 14 Feb 2019 23:59:50 -0600 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=filipjaniszewski.com; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=ZgLYflhwCfgkjmsIZ6WcziJeNP6GG0TBfgg4bKgXB2s=; b=yDtBHfc1Ona0F8UyU3+8GFm51q a1F4ika6NPIYs6p94gIISR8l7wrauU+bH/1vTphZLS6oaFL82ThYDqK2awt3+lvL0d6FQLwmYMlpV yC1Xj2sUKVOrijzyvPBvCzxktbmCtDimdfrbfQCvp+PPDEkFsbjHUPbziYXZKozcDwMVfVay7g1s2 5azosSCBitEpWT6oJcan1FnxqLerTwOY+TpxKidoga1v/480vUsyKHf7jdlQH2I41HvGWO5MK/kT/ ZNhYYDPsylfZY6rMEHB5FGQzQ5biRiLSAgG44TYDQC9OFlj5Jaez/8R4fUMEhBiy0S0ZuKY/H7BUJ wk18taFw==; Received: from [89.64.173.160] (port=57642 helo=localhost.localdomain) by es18.siteground.eu with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_34-9f6032f-XX) (envelope-from ) id 1guWXJ-00077A-II; Fri, 15 Feb 2019 06:59:45 +0100 To: "users@dpdk.org" Cc: "Wiles, Keith" References: <4bd38b68-02e7-f031-5627-2bd2c9a38333@filipjaniszewski.com> <95B2277E-2E64-4703-97C3-022967A7F175@intel.com> <2ACB2CB5-241D-44AC-8203-5E2827885150@intel.com> From: Filip Janiszewski Message-ID: Date: Fri, 15 Feb 2019 06:59:44 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <2ACB2CB5-241D-44AC-8203-5E2827885150@intel.com> Content-Type: text/plain; charset=iso-8859-15 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: 37.60.250.193 X-SpamExperts-Domain: es18.siteground.eu X-SpamExperts-Username: 37.60.250.193 Authentication-Results: mailspamprotection.com; auth=pass smtp.auth=37.60.250.193@es18.siteground.eu X-SpamExperts-Outgoing-Class: ham X-SpamExperts-Outgoing-Evidence: Combined (0.12) X-Recommended-Action: accept X-Filter-ID: EX5BVjFpneJeBchSMxfU5iNyksltX5kQGcQ9zKkgGjd602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvOxITnAXRqFyrMxs2kFsBK+f+icj1Tmt3okA+BmaGqk1Rpmsn7HjZIyvst3B2ujNFVefH zJ6mVE7ewsipSVIfs4bVRLjkwSA+DqVQMmFfY+SR1UoIZHeGiHTv13xbWqFGxcWfi5SA8F1F1Wf2 ytQ9CW1li19mW0G91CSooRJqA7sIn7yttJWcfDN/UT6/wnDi5b6NjhToz7AbkSS/ihTHoF6htohM oxLNurLxItwRYhKjUAsAEp7he0osUq/5XwU41W6noxJ1R+JPOFQkdVRSeviFcFhO9Ph08zfxywcA n5Te8dcxvnQYERkMuRL5/fo3RNhLla8JCfjz6HFCYJ5nqvIDuONzMRaL3IMJceeVmuMY+GQ66azi oBnt+leQ7P/PJYubkfpBG83WrynQ+RDP1axbO+uWqv+yIXuSaTRGCFbDjMhpwyKUnIZXKOkSA6DY P9CWUDl6hp96RIaeG6P8U6RGPYZZXkvmZIcO+5pLCnX7Aidax8CimApmOijfm+KR6wEiRQv+PVjj wa+Z5RFCOMSE6kYaEnAxIqj9q/AUkKR5ipB4LeUye0Gt8URvpfAz3uadQLVBY+t7yeN1NrHolSCk B8uPD3+K56pbcHH0yaDkxBgNDwC2RyZ3Myva+Ht3FCYvKG65C/agdaikX5noCmRl+a9ebC4HtNxM V3vaRMdf0XgpjLWVcVX/NL+TV1IncVwzwH8PmaYM7dkOmig/i7nQ6K+hWn20Xa7wm3FEAmDIh2Ui LwsEPenX6d9KCOHDE/djzQ6YC7Heg3Xf7O1TOd6OulNIqZXYB+cre9M3D4ITzqK7bD6jt101eZGN 3LCiLKBhhCQYRTB6WcTibv/ZaKsZhAExSnVh2DoK5j0TieQyZuM7jUXIESohoO51xWmU8fqMJ3br gkR11wiq2J3hdtypR//dWyN05FDiM40BH66RmOX0sSNl99m9kIF/bxXfe8hoJUyrl5Dn+x288sHh sig1lfwBlzoNEpB9QCKXQ/ZsV9ECIyIwp9c70LlMQgcOCbJ2jDiWgMo75XZKz3zNgmesfcctQgz0 xq+sj+/1/JOsUfLgDUYOHgGMkeTmlKV8RdYNisEeNVs6ZVLKIeiuSHI= X-Report-Abuse-To: spam@quarantine1.mailspamprotection.com Subject: Re: [dpdk-users] RX of multi-segment jumbo frames X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Feb 2019 05:59:51 -0000 Unfortunately I didn't get much help from the maintainers at Mellanox, but I discovered that with DPDK 18.05 there's the flag ignore_offload_bitfield which once toggled to 1 along with the offloads set to DEV_RX_OFFLOAD_JUMBO_FRAME|DEV_RX_OFFLOAD_SCATTER allows DPDK to capture Jumbo on Mellanox: https://doc.dpdk.org/api-18.05/structrte__eth__rxmode.html In DPDK 19.02 this flag is missing and I can't capture Jumbos with my current configuration. Sadly, even if setting ignore_offload_bitfield to 1 fix my problem it creates a bunch more, the packets coming in are not timestamped for example (setting hw_timestamp to 1 does not fix the issue as the timestamp are still EPOCH + some ms.). Not sure if this can trigger any idea, for me it is not completely clear what was the purpose of ignore_offload_bitfield (removed later) and how to enable Jumbos properly. What I've attempted so far (apart from the ignore_offload_bitfield): 1) Set mtu to 9600 (rte_eth_dev_set_mtu) 2) Configure port with offloads DEV_RX_OFFLOAD_SCATTER | DEV_RX_OFFLOAD_JUMBO_FRAME, max_rx_pkt_len set to 9600 3) Configure RX queue with default_rxconf (from rte_eth_dev_info) adding the offloads from the port configuration (DEV_RX_OFFLOAD_SCATTER | DEV_RX_OFFLOAD_JUMBO_FRAME) The JF are reported as ierror in rte_eth_stats. Thanks Il 09/02/19 16:36, Wiles, Keith ha scritto: > > >> On Feb 9, 2019, at 9:27 AM, Filip Janiszewski wrote: >> >> >> >> Il 09/02/19 14:51, Wiles, Keith ha scritto: >>> >>> >>>> On Feb 9, 2019, at 5:11 AM, Filip Janiszewski wrote: >>>> >>>> Hi, >>>> >>>> I'm attempting to receive jumbo frames (~9000 bytes) on a Mellonox card >>>> using DPDK, I've configured the DEV_RX_OFFLOAD_JUMBO_FRAME offload for >>>> rte_eth_conf and rte_eth_rxconf (per RX Queue), but I can capture jumbo >>>> frames only if the mbuf is large enough to contain the whole packet, is >>>> there a way to enable DPDK to chain the incoming data in mbufs smaller >>>> than the actual packet? >>>> >>>> We don't have many of those big packets coming in, so would be optimal >>>> to leave the mbuf size to RTE_MBUF_DEFAULT_BUF_SIZE and then configure >>>> the RX device to chain those bufs for larger packets, but can't find a >>>> way to do it, any suggestion? >>>> >>> >>> the best i understand is the nic or pmd needs to be configured to split up packets between mbufs in the rx ring. i look in the docs for the nic and see if it supports splitting up packets or ask the maintainer from the maintainers file. >> >> I can capture jumbo packets with Wireshark on the same card (same port, >> same setup), which let me think the problem is purely on my DPDK card >> configuration. >> >> According to ethtools, the jumbo packet (from now on JF, Jumbo Frame) is >> detected at phy level, the couters rx_packets_phy, rx_bytes_phy, >> rx_8192_to_10239_bytes_phy are properly increased. >> >> There was an option to setup manually the support for JF but was remove >> from DPDK after version 16.07: CONFIG_RTE_LIBRTE_MLX5_SGE_WR_N. >> According to the release note: >> >> . >> Improved jumbo frames support, by dynamically setting RX scatter gather >> elements according to the MTU and mbuf size, no need for compilation >> parameter ``MLX5_PMD_SGE_WR_N`` >> . >> >> Not quire sure where to look for.. >> > > maintainer is your best bet now. >>>> Thanks >>>> >>>> -- >>>> BR, Filip >>>> +48 666 369 823 >>> >>> Regards, >>> Keith >>> >> >> -- >> BR, Filip >> +48 666 369 823 > > Regards, > Keith > -- BR, Filip +48 666 369 823