From: "Michael S. Tsirkin" <mst@redhat.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: Jason Wang <jasowang@redhat.com>,
Network Development <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next 0/3] support changing steering policies in tuntap
Date: Sun, 1 Oct 2017 06:28:04 +0300 [thread overview]
Message-ID: <20171001062520-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAF=yD-KuDZK0-YUfYde=dk_6M6fgj_opuiK2VTfCKDM_=MqDcw@mail.gmail.com>
On Thu, Sep 28, 2017 at 12:09:05PM -0400, Willem de Bruijn wrote:
> Programming from the guest is
> indeed different. I don't fully understand that use case.
Generally programming host BPF from guest is a clear win - think DOS
protection. Guest runs logic to detect dos attacks, then passes the
program to host. Afterwards, host does not need to enter guest if
there's a DOS attack. Saves a ton of cycles.
The difficulty is making it work well, e.g. how do we handle maps?
--
MST
next prev parent reply other threads:[~2017-10-01 3:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 8:23 [PATCH net-next 0/3] support changing steering policies in tuntap Jason Wang
2017-09-27 8:23 ` [PATCH net-next 1/3] tun: abstract flow steering logic Jason Wang
2017-09-27 8:23 ` [PATCH net-next 2/3] tun: introduce ioctls to set and get steering policies Jason Wang
2017-09-27 8:23 ` [PATCH net-next 3/3] tun: introduce cpu id based steering policy Jason Wang
2017-09-27 22:13 ` [PATCH net-next 0/3] support changing steering policies in tuntap Michael S. Tsirkin
2017-09-27 23:25 ` Willem de Bruijn
2017-09-28 5:02 ` Tom Herbert
2017-09-28 7:53 ` Jason Wang
2017-09-28 7:23 ` Jason Wang
2017-09-28 16:09 ` Willem de Bruijn
2017-09-29 9:41 ` Jason Wang
2017-10-01 3:28 ` Michael S. Tsirkin [this message]
2017-09-28 6:50 ` Jason Wang
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=20171001062520-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=willemdebruijn.kernel@gmail.com \
/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.