All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Sherwood <rob.sherwood@gmail.com>
To: aforster@cloudflare.com
Cc: justin.azoff@gmail.com, xdp-newbies@vger.kernel.org
Subject: Re: AF_XDP umem and jumbo frames?
Date: Wed, 26 Sep 2018 17:55:24 -0700	[thread overview]
Message-ID: <CAFg6RxsSRzww4f3n6xH1gRWQfXhhHkk0oZNSWNc6+kHT0p_VeQ@mail.gmail.com> (raw)
In-Reply-To: <CAKxSbF0yn0s5JEbWsF65uwEB6sCThhvJ8kpuOVCNaf=diFxjyA@mail.gmail.com>

Thanks for the reference and the page-per-packet point makes sense.
At the same time, not supporting jumbo frames seems like a non-trivial
limitation.  Are there a subset of drivers that do support jumbo
frames (or LRO or the other features that require multiple pages per
packet)?

Thanks in advance,

- Rob
.
On Tue, Sep 25, 2018 at 9:44 AM Alex Forster <aforster@cloudflare.com> wrote:
>
> > On my test box running 4.18 if XDP is in use the MTU can not be set higher than 3050.
>
> Ah, that answers a few questions for me. Thanks!
>
> Alex Forster

  reply	other threads:[~2018-09-27  7:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24 21:52 AF_XDP umem and jumbo frames? Alex Forster
2018-09-24 23:15 ` Justin Azoff
2018-09-25 16:43   ` Alex Forster
2018-09-27  0:55     ` Rob Sherwood [this message]
2018-10-04  6:44       ` Björn Töpel
2018-10-04  7:52         ` Jesper Dangaard Brouer
2018-10-04 14:48           ` Justin Azoff
2018-10-04 15:39           ` Alex Forster
2018-10-04 15:47           ` Rob Sherwood
2018-10-04 19:44             ` Jesper Dangaard Brouer
2018-10-05 18:47               ` Zvi Effron
2018-10-07 15:14                 ` Jesper Dangaard Brouer
2018-10-05 19:56               ` Justin Azoff
2018-10-07 16:13                 ` Jesper Dangaard Brouer
2018-10-07 17:48                   ` Eric Leblond
2018-10-07 19:34                   ` Johannes Berg
2018-10-06 20:02               ` Rob Sherwood

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=CAFg6RxsSRzww4f3n6xH1gRWQfXhhHkk0oZNSWNc6+kHT0p_VeQ@mail.gmail.com \
    --to=rob.sherwood@gmail.com \
    --cc=aforster@cloudflare.com \
    --cc=justin.azoff@gmail.com \
    --cc=xdp-newbies@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.