DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burdick, Cliff" <Cliff.Burdick@viasat.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH] Added jumboframe RX offload flag in example using 9KB packets
Date: Tue, 6 Nov 2018 23:06:09 +0000	[thread overview]
Message-ID: <03A7D9A58FAFB54FBB01FEE199D7308A0134B8BDDB@wdc1exchmbxp02.hq.corp.viasat.com> (raw)

I apologize if any formatting is wrong here, since this is my first post. I noticed with i40e jumboframes cannot be received without the offload flag set, even though the max_rx_pkt_len is set to 9000. This is the case in the ip_pipeline example, so I don't think packets that large would work until the offload is set.



Signed-off-by: Cliff Burdick <cliff.burdick@viasat.com>

---

examples/ip_pipeline/link.c | 1 +

1 file changed, 1 insertion(+)



diff --git a/examples/ip_pipeline/link.c b/examples/ip_pipeline/link.c index 787eb866a..45d55cd1f 100644

--- a/examples/ip_pipeline/link.c

+++ b/examples/ip_pipeline/link.c

@@ -48,6 +48,7 @@ static struct rte_eth_conf port_conf_default = {

                               .mq_mode = ETH_MQ_RX_NONE,

                               .max_rx_pkt_len = 9000, /* Jumbo frame max packet len */

                               .split_hdr_size = 0, /* Header split buffer size */

+                             .offloads = DEV_RX_OFFLOAD_JUMBO_FRAME,

               },

               .rx_adv_conf = {

                               .rss_conf = {

--

2.17.1

                 reply	other threads:[~2018-11-06 23:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=03A7D9A58FAFB54FBB01FEE199D7308A0134B8BDDB@wdc1exchmbxp02.hq.corp.viasat.com \
    --to=cliff.burdick@viasat.com \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).