From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Lawrence Brakmo <brakmo@fb.com>
Cc: netdev <netdev@vger.kernel.org>, Kernel Team <kernel-team@fb.com>,
Alexei Starovoitov <ast@fb.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Blake Matheny <bmatheny@fb.com>
Subject: Re: [PATCH net-next 3/5] bpf: Add BPF_SOCKET_OPS_BASE_RTT support to tcp_nv
Date: Sat, 21 Oct 2017 12:37:17 -0700 [thread overview]
Message-ID: <20171021193715.5cdwmeuseklqnkyc@ast-mbp> (raw)
In-Reply-To: <20171020180543.4156833-4-brakmo@fb.com>
On Fri, Oct 20, 2017 at 11:05:41AM -0700, Lawrence Brakmo wrote:
> TCP_NV will try to get the base RTT from a socket_ops BPF program if one
> is loaded. NV will then use the base RTT to bound its min RTT (its
> notion of the base RTT). It uses the base RTT as an upper bound and 80%
> of the base RTT as its lower bound.
...
> Signed-off-by: Lawrence Brakmo <brakmo@fb.com>
> Acked_by: Alexei Starovoitov <ast@fb.com>
^
just noticed the typo above :)
fixing it with:
Acked-by: Alexei Starovoitov <ast@kernel.org>
so patchworks can pick it up automatically.
next prev parent reply other threads:[~2017-10-21 19:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 18:05 [PATCH net-next 0/5] bpf: add support for BASE_RTT Lawrence Brakmo
2017-10-20 18:05 ` [PATCH net-next 1/5] bpf: add support for BPF_SOCK_OPS_BASE_RTT Lawrence Brakmo
2017-10-20 18:05 ` [PATCH net-next 2/5] bpf: Adding helper function bpf_getsockops Lawrence Brakmo
2017-10-20 18:05 ` [PATCH net-next 3/5] bpf: Add BPF_SOCKET_OPS_BASE_RTT support to tcp_nv Lawrence Brakmo
2017-10-21 19:37 ` Alexei Starovoitov [this message]
2017-10-20 18:05 ` [PATCH net-next 4/5] bpf: sample BPF_SOCKET_OPS_BASE_RTT program Lawrence Brakmo
2017-10-20 18:05 ` [PATCH net-next 5/5] bpf: create samples/bpf/tcp_bpf.readme Lawrence Brakmo
2017-10-22 2:12 ` [PATCH net-next 0/5] bpf: add support for BASE_RTT David Miller
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=20171021193715.5cdwmeuseklqnkyc@ast-mbp \
--to=alexei.starovoitov@gmail.com \
--cc=ast@fb.com \
--cc=bmatheny@fb.com \
--cc=brakmo@fb.com \
--cc=daniel@iogearbox.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