From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Martin KaFai Lau <kafai@fb.com>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
David Miller <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Kernel Team <kernel-team@fb.com>,
Network Development <netdev@vger.kernel.org>
Subject: Re: [PATCH v3 bpf-next 0/3] bpf: tcp: Add bpf_cubic example
Date: Wed, 22 Jan 2020 16:40:53 -0800 [thread overview]
Message-ID: <CAADnVQJ1EWCJEiPRMMYF-m57FEGCTjPmzkx3XtF6gC=sDeNg1A@mail.gmail.com> (raw)
In-Reply-To: <20200122233639.903041-1-kafai@fb.com>
On Wed, Jan 22, 2020 at 3:37 PM Martin KaFai Lau <kafai@fb.com> wrote:
>
> This set adds bpf_cubic.c example. It was separated from the
> earlier BPF STRUCT_OPS series. Some highlights since the
> last post:
>
> 1. It is based on EricD recent fixes to the kernel tcp_cubic. [1]
> 2. The bpf jiffies reading helper is inlined by the verifier.
> Different from the earlier version, it only reads jiffies alone
> and does not do usecs/jiffies conversion.
> 3. The bpf .kconfig map is used to read CONFIG_HZ.
>
> [1]: https://patchwork.ozlabs.org/cover/1215066/
>
> v3:
> - Remove __weak from CONFIG_HZ in patch 3. (Andrii)
Applied. Thanks
prev parent reply other threads:[~2020-01-23 0:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 23:36 [PATCH v3 bpf-next 0/3] bpf: tcp: Add bpf_cubic example Martin KaFai Lau
2020-01-22 23:36 ` [PATCH v3 bpf-next 1/3] bpf: Add BPF_FUNC_jiffies64 Martin KaFai Lau
2020-01-22 23:36 ` [PATCH v3 bpf-next 2/3] bpf: Sync uapi bpf.h to tools/ Martin KaFai Lau
2020-01-22 23:36 ` [PATCH v3 bpf-next 3/3] bpf: tcp: Add bpf_cubic example Martin KaFai Lau
2020-01-23 0:40 ` 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='CAADnVQJ1EWCJEiPRMMYF-m57FEGCTjPmzkx3XtF6gC=sDeNg1A@mail.gmail.com' \
--to=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kafai@fb.com \
--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).