From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>, davem@davemloft.net
Cc: daniel@iogearbox.net, andrii@kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH bpf-next 0/4] libbpf: Move CO-RE logic into separate file.
Date: Thu, 22 Jul 2021 18:02:09 +0200 [thread overview]
Message-ID: <871r7q8hha.fsf@toke.dk> (raw)
In-Reply-To: <20210721000822.40958-1-alexei.starovoitov@gmail.com>
Alexei Starovoitov <alexei.starovoitov@gmail.com> writes:
> From: Alexei Starovoitov <ast@kernel.org>
>
> Split CO-RE processing logic from libbpf into separate file
> with an interface that doesn't dependend on libbpf internal details.
> As the next step relo_core.c will be compiled with libbpf and with the kernel.
Interesting! What's the use case for having it in the kernel as well? :)
-Toke
next prev parent reply other threads:[~2021-07-22 16:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 0:08 [PATCH bpf-next 0/4] libbpf: Move CO-RE logic into separate file Alexei Starovoitov
2021-07-21 0:08 ` [PATCH bpf-next 1/4] libbpf: Cleanup the layering between CORE and bpf_program Alexei Starovoitov
2021-07-21 0:08 ` [PATCH bpf-next 2/4] libbpf: Split bpf_core_apply_relo() into bpf_program indepdent helper Alexei Starovoitov
2021-07-21 0:08 ` [PATCH bpf-next 3/4] libbpf: Move CO-RE types into relo_core.h Alexei Starovoitov
2021-07-21 0:08 ` [PATCH bpf-next 4/4] libbpf: Split CO-RE logic into relo_core.c Alexei Starovoitov
2021-07-22 16:02 ` Toke Høiland-Jørgensen [this message]
2021-07-24 0:23 ` [PATCH bpf-next 0/4] libbpf: Move CO-RE logic into separate file Alexei Starovoitov
2021-07-26 19:37 ` Andrii Nakryiko
2021-07-28 4:49 ` Alexei Starovoitov
2021-07-29 18:43 ` Andrii Nakryiko
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=871r7q8hha.fsf@toke.dk \
--to=toke@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kernel-team@fb.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 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).