From: Konstantinos Kaffes <kkaffes@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: bpf@vger.kernel.org
Subject: Re: [QUESTION] TCP connected socket selection
Date: Mon, 11 Jan 2021 11:48:47 -0800 [thread overview]
Message-ID: <CAHAzn3o4HQQAXXnGg8My14z8dJmREkVDsBheNtxwtNHZB+xp-Q@mail.gmail.com> (raw)
In-Reply-To: <20210111111949.18236404@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On Mon, 11 Jan 2021 at 11:19, Jakub Kicinski <kuba@kernel.org> wrote:
>
> On Mon, 11 Jan 2021 10:33:49 -0800 Konstantinos Kaffes wrote:
> > Hi everyone,
> >
> > It is the first time I am posting to a kernel mailing list so please
> > let me know if this question needs to be directed elsewhere.
> >
> > I have been using BPF to programmatically steer UDP datagrams to
> > sockets using the "sk_reuseport" hook.
> >
> > Similarly, I would like to identify request boundaries within a TCP
> > stream/connection and programmably forward requests to different
> > sockets *after* a connection is established. Is there a way to do that
> > in the kernel using BPF?
>
> Sounds like what KCM does.
Thanks! KCM would work but it is unclear to me how I can specify the
policy used by the multiplexor to match messages to specific sockets.
The documentation has examples on how to do the delineation but
nothing on how to specify the matching policy.
prev parent reply other threads:[~2021-01-11 19:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 18:33 [QUESTION] TCP connected socket selection Konstantinos Kaffes
2021-01-11 19:19 ` Jakub Kicinski
2021-01-11 19:48 ` Konstantinos Kaffes [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=CAHAzn3o4HQQAXXnGg8My14z8dJmREkVDsBheNtxwtNHZB+xp-Q@mail.gmail.com \
--to=kkaffes@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=kuba@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 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).