From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, jasowang@redhat.com,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, john.fastabend@gmail.com
Subject: Re: [PATCH v2] virtio_net: fix PAGE_SIZE > 64k
Date: Tue, 24 Jan 2017 22:45:37 +0200 [thread overview]
Message-ID: <20170124221114-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20170124.150959.1708982899683381291.davem@davemloft.net>
On Tue, Jan 24, 2017 at 03:09:59PM -0500, David Miller wrote:
> From: "Michael S. Tsirkin" <mst@redhat.com>
> Date: Tue, 24 Jan 2017 21:53:13 +0200
>
> > I didn't realise. Why can't we? I thought that adjust_header is an
> > optional feature that userspace can test for, so no rush.
>
> No, we want the base set of XDP features to be present in all drivers
> supporting XDP.
I see, I didn't realize this. In light of this, is there any
guidance *how much* head room is required to be considered
valid? We already have 12 bytes of headroom.
I'm generally sorry it's taking long, a large part of that is difficulty
figuring out the requirements: when we discussed this on LPC my
take-away was that one of the first users will be fighting DDOS attacks.
In light of this, I assumed that
- supporting just DROP (or DROP+TX) would already be useful
- XDP_PASS shouldn't be too slow as some people will run all
their traffic with XDP enabled
- people actually want this in virtio because they run in a vm
Since then I heard opinions that seem to imply that
- you must support all features, not just DROP, otherwise it's useless
- XDP_PASS is a slow path fallback as people are not expected to mix XDP
with regular sockets
- DDOS protection and by extension XDP in virtio is a developer's toy anyway
Thus, expect some slowness while I figure it all out.
--
MST
next prev parent reply other threads:[~2017-01-24 20:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 19:37 [PATCH v2] virtio_net: fix PAGE_SIZE > 64k Michael S. Tsirkin
2017-01-24 19:42 ` David Miller
2017-01-24 19:53 ` Michael S. Tsirkin
2017-01-24 20:09 ` David Miller
2017-01-24 20:45 ` Michael S. Tsirkin [this message]
2017-01-24 20:53 ` David Miller
2017-01-24 21:07 ` Michael S. Tsirkin
2017-01-24 21:10 ` David Miller
2017-01-24 21:56 ` Michael S. Tsirkin
2017-01-25 3:48 ` John Fastabend
-- strict thread matches above, loose matches on Subject: below --
2017-01-25 4:07 Alexei Starovoitov
2017-01-25 14:23 ` Michael S. Tsirkin
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=20170124221114-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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).