From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: john.fastabend@gmail.com, davejwatson@fb.com, netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 0/8] sockmap integration for ktls
Date: Mon, 15 Oct 2018 12:27:47 -0700 [thread overview]
Message-ID: <20181015192745.w24c6vjzvxk27fhk@ast-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20181013004603.3747-1-daniel@iogearbox.net>
On Sat, Oct 13, 2018 at 02:45:55AM +0200, Daniel Borkmann wrote:
> This work adds a generic sk_msg layer and converts both sockmap
> and later ktls over to make use of it as a common data structure
> for application data (similarly as sk_buff for network packets).
> With that in place the sk_msg framework spans accross ULP layer
> in the kernel and allows for introspection or filtering of L7
> data with the help of BPF programs operating on a common input
> context.
>
> In a second step, we enable the latter for ktls which was previously
> not possible, meaning, ktls and sk_msg verdict programs were
> mutually exclusive in the ULP layer which created challenges for
> the orchestrator when trying to apply TCP based policy, for
> example. Leveraging the prior consolidation we can finally overcome
> this limitation.
>
> Note, there's no change in behavior when ktls is not used in
> combination with BPF, and also no change in behavior for stand
> alone sockmap. The kselftest suites for ktls, sockmap and ktls
> with sockmap combined also runs through successfully. For further
> details please see individual patches.
>
> Thanks!
>
> v1 -> v2:
> - Removed leftover comment spotted by Alexei
> - Improved commit messages, rebase
Applied, Thanks
prev parent reply other threads:[~2018-10-16 3:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-13 0:45 [PATCH bpf-next v2 0/8] sockmap integration for ktls Daniel Borkmann
2018-10-13 0:45 ` [PATCH bpf-next v2 1/8] tcp, ulp: enforce sock_owned_by_me upon ulp init and cleanup Daniel Borkmann
2018-10-16 14:17 ` Eric Dumazet
2018-10-16 14:29 ` Daniel Borkmann
2018-10-13 0:45 ` [PATCH bpf-next v2 2/8] tcp, ulp: remove ulp bits from sockmap Daniel Borkmann
2018-10-13 0:45 ` [PATCH bpf-next v2 3/8] bpf, sockmap: convert to generic sk_msg interface Daniel Borkmann
2018-10-13 0:45 ` [PATCH bpf-next v2 4/8] tls: " Daniel Borkmann
2018-10-17 14:55 ` Eric Dumazet
2018-10-17 17:32 ` Daniel Borkmann
2018-10-13 0:46 ` [PATCH bpf-next v2 5/8] tls: replace poll implementation with read hook Daniel Borkmann
2018-10-13 0:46 ` [PATCH bpf-next v2 6/8] tls: add bpf support to sk_msg handling Daniel Borkmann
2018-10-13 0:46 ` [PATCH bpf-next v2 7/8] bpf: add tls support for testing in test_sockmap Daniel Borkmann
2018-10-16 0:42 ` Andrey Ignatov
2018-10-16 0:48 ` Daniel Borkmann
2018-10-13 0:46 ` [PATCH bpf-next v2 8/8] bpf, doc: add maintainers entry to related files Daniel Borkmann
2018-10-15 19:27 ` Alexei Starovoitov [this message]
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=20181015192745.w24c6vjzvxk27fhk@ast-mbp.dhcp.thefacebook.com \
--to=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davejwatson@fb.com \
--cc=john.fastabend@gmail.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.