From: Martin Lau <firstname.lastname@example.org> To: Jakub Sitnicki <email@example.com> Cc: "firstname.lastname@example.org" <email@example.com>, John Fastabend <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org> Subject: Re: [RFC bpf-next 0/5] Extend SOCKMAP to store listening sockets Date: Mon, 28 Oct 2019 20:42:59 +0000 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Mon, Oct 28, 2019 at 01:35:26PM +0100, Jakub Sitnicki wrote: > On Mon, Oct 28, 2019 at 06:52 AM CET, Martin Lau wrote: > > On Tue, Oct 22, 2019 at 01:37:25PM +0200, Jakub Sitnicki wrote: > >> This patch set is a follow up on a suggestion from LPC '19 discussions to > >> make SOCKMAP (or a new map type derived from it) a generic type for storing > >> established as well as listening sockets. > >> > >> We found ourselves in need of a map type that keeps references to listening > >> sockets when working on making the socket lookup programmable, aka BPF > >> inet_lookup . Initially we repurposed REUSEPORT_SOCKARRAY but found it > >> problematic to extend due to being tightly coupled with reuseport > >> logic (see slides ). > >> So we've turned our attention to SOCKMAP instead. > >> > >> As it turns out the changes needed to make SOCKMAP suitable for storing > >> listening sockets are self-contained and have use outside of programming > >> the socket lookup. Hence this patch set. > >> > >> With these patches SOCKMAP can be used in SK_REUSEPORT BPF programs as a > >> drop-in replacement for REUSEPORT_SOCKARRAY for TCP. This can hopefully > >> lead to code consolidation between the two map types in the future. > > What is the plan for UDP support in sockmap? > > It's on our road-map because without SOCKMAP support for UDP we won't be > able to move away from TPROXY  and custom SO_BINDTOPREFIX extension >  for steering new UDP flows to receiving sockets. Also we would like > to look into using SOCKMAP for connected UDP socket splicing in the > future . > > I was planning to split work as follows: > > 1. SOCKMAP support for listening sockets (this series) > 2. programmable socket lookup for TCP (cut-down version of ) > 3. SOCKMAP support for UDP (work not started) hmm...It is hard to comment how the full UDP sockmap may work out without a code attempt because I am not fluent in sock_map ;) From a quick look, it seems there are quite a few things to do. For example, the TCP_SKB_CB(skb) usage and how that may look like in UDP. "struct udp_skb_cb" is 28 bytes while "struct napi_gro_cb" seems to be 48 bytes already which may need a closer look. > 4. programmable socket lookup for UDP (rest of ) > > I'm open to suggestions on how to organize it. > > >> Having said that, the main intention here is to lay groundwork for using > >> SOCKMAP in the next iteration of programmable socket lookup patches. > > What may be the minimal to get only lookup work for UDP sockmap? > > .close() and .unhash()? > > John would know better. I haven't tried doing it yet. > > From just reading the code - override the two proto ops you mentioned, > close and unhash, and adapt the socket checks in SOCKMAP. Do your use cases need bpf prog attached to sock_map? If not, would it be cleaner to delicate another map_type for lookup-only use case to have both TCP and UDP support. > > -Jakub > >  https://urldefense.proofpoint.com/v2/url?u=https-3A__blog.cloudflare.com_how-2Dwe-2Dbuilt-2Dspectrum_&d=DwIBAg&c=5VD0RTtNlTh3ycd41b3MUw&r=VQnoQ7LvghIj0gVEaiQSUw&m=lSo-FsOeNl_8znZZ07H8I6ZYAinPKTR5C3Cn_Ol3QYQ&s=DZgW8-2Xl1P8NU59ji4ieQLzwWpx4t3gGq_tqB0l3Bo&e= >  https://email@example.com/ >  https://firstname.lastname@example.org/ >  https://urldefense.proofpoint.com/v2/url?u=https-3A__blog.cloudflare.com_sockmap-2Dtcp-2Dsplicing-2Dof-2Dthe-2Dfuture_&d=DwIBAg&c=5VD0RTtNlTh3ycd41b3MUw&r=VQnoQ7LvghIj0gVEaiQSUw&m=lSo-FsOeNl_8znZZ07H8I6ZYAinPKTR5C3Cn_Ol3QYQ&s=NerUqb4j7IsGBTcni6Yxk40wf6kTkckHXn3Nx5i4mCU&e=
next prev parent reply other threads:[~2019-10-28 20:43 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-22 11:37 Jakub Sitnicki 2019-10-22 11:37 ` [RFC bpf-next 1/5] bpf, sockmap: Let BPF helpers use lookup operation on SOCKMAP Jakub Sitnicki 2019-10-24 16:59 ` John Fastabend 2019-10-22 11:37 ` [RFC bpf-next 2/5] bpf, sockmap: Allow inserting listening TCP sockets into SOCKMAP Jakub Sitnicki 2019-10-24 17:06 ` John Fastabend 2019-10-25 9:41 ` Jakub Sitnicki 2019-10-22 11:37 ` [RFC bpf-next 3/5] bpf, sockmap: Don't let child socket inherit psock or its ops on copy Jakub Sitnicki 2019-10-22 11:37 ` [RFC bpf-next 4/5] bpf: Allow selecting reuseport socket from a SOCKMAP Jakub Sitnicki 2019-10-22 11:37 ` [RFC bpf-next 5/5] selftests/bpf: Extend SK_REUSEPORT tests to cover SOCKMAP Jakub Sitnicki 2019-10-24 16:12 ` [RFC bpf-next 0/5] Extend SOCKMAP to store listening sockets Alexei Starovoitov 2019-10-24 16:56 ` John Fastabend 2019-10-25 9:26 ` Jakub Sitnicki 2019-10-25 14:18 ` John Fastabend 2019-10-28 5:52 ` Martin Lau 2019-10-28 12:35 ` Jakub Sitnicki 2019-10-28 19:04 ` John Fastabend 2019-10-29 8:56 ` Jakub Sitnicki 2019-10-28 20:42 ` Martin Lau [this message] 2019-10-28 21:05 ` John Fastabend 2019-10-28 21:38 ` Martin Lau 2019-10-29 8:52 ` Jakub Sitnicki
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [RFC bpf-next 0/5] Extend SOCKMAP to store listening sockets' \ /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
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).