From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: John Fastabend <john.fastabend@gmail.com>,
john.r.fastabend@intel.com, netdev@vger.kernel.org,
alexei.starovoitov@gmail.com, daniel@iogearbox.net
Subject: Re: [net PATCH] net: virtio: cap mtu when XDP programs are running
Date: Tue, 10 Jan 2017 16:51:03 +0200 [thread overview]
Message-ID: <20170110164654-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20170110044910-mutt-send-email-mst@kernel.org>
On Tue, Jan 10, 2017 at 04:51:34AM +0200, Michael S. Tsirkin wrote:
> XDP seems to have a bunch of weird restrictions, I just
> do not like it that the logic spills out to all drivers.
> What if someone decides to extend it to two pages in the future?
> Recode it all in all drivers ...
>
> Why can't net core enforce mtu?
And BTW limits on MTU are a problem that will have to be
addressed sooner or later, disabling offloads on the NIC
is one thing, but reconfiguring all of the network
with a lower MTU is another.
> --
> MST
next prev parent reply other threads:[~2017-01-10 14:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 22:30 [net PATCH] net: virtio: cap mtu when XDP programs are running John Fastabend
2017-01-03 6:14 ` Jason Wang
2017-01-03 16:48 ` John Fastabend
2017-01-04 3:16 ` Jason Wang
2017-01-04 18:57 ` John Fastabend
2017-01-05 3:09 ` Jason Wang
2017-01-09 23:05 ` Michael S. Tsirkin
2017-01-09 23:13 ` John Fastabend
2017-01-09 23:24 ` Michael S. Tsirkin
2017-01-09 23:49 ` John Fastabend
2017-01-09 23:58 ` Michael S. Tsirkin
2017-01-10 2:29 ` Jason Wang
2017-01-10 2:51 ` Michael S. Tsirkin
2017-01-10 3:30 ` John Fastabend
2017-01-10 3:55 ` Michael S. Tsirkin
2017-01-10 4:25 ` John Fastabend
2017-01-10 5:00 ` Michael S. Tsirkin
2017-01-11 3:37 ` Jason Wang
2017-01-10 3:34 ` Jason Wang
2017-01-10 14:51 ` Michael S. Tsirkin [this message]
2017-01-03 16:48 ` John Fastabend
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=20170110164654-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--cc=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=john.r.fastabend@intel.com \
--cc=netdev@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.