From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Geliang Tang <geliang.tang@suse.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v22 0/5] BPF redundant scheduler, part 2
Date: Mon, 5 Dec 2022 17:13:47 -0800 (PST) [thread overview]
Message-ID: <a65197b3-6504-9b89-315a-76f7b5f92eec@linux.intel.com> (raw)
In-Reply-To: <cover.1669987293.git.geliang.tang@suse.com>
On Fri, 2 Dec 2022, Geliang Tang wrote:
> v22:
> - update patch 2 as Mat suggested.
> - patch 4 and 5 in v21 will send later.
Ok, thanks for the note on v21 patches 4/5. My only other comments on v22
are on patches 2 & 3 (already replied on those).
- Mat
>
> v21:
> - address Mat's comments in v20.
> - redundant sends on retransmit code path.
>
> v20:
> - rebased on "Squash to "mptcp: refactor push_pending logic" v19"
>
--
Mat Martineau
Intel
prev parent reply other threads:[~2022-12-06 1:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 13:30 [PATCH mptcp-next v22 0/5] BPF redundant scheduler, part 2 Geliang Tang
2022-12-02 13:30 ` [PATCH mptcp-next v22 1/5] mptcp: add scheduler wrappers Geliang Tang
2022-12-02 13:30 ` [PATCH mptcp-next v22 2/5] mptcp: use get_send wrapper Geliang Tang
2022-12-06 1:09 ` Mat Martineau
2022-12-02 13:30 ` [PATCH mptcp-next v22 3/5] mptcp: use get_retrans wrapper Geliang Tang
2022-12-06 1:10 ` Mat Martineau
2022-12-02 13:30 ` [PATCH mptcp-next v22 4/5] selftests/bpf: Add bpf_red scheduler Geliang Tang
2022-12-02 13:30 ` [PATCH mptcp-next v22 5/5] selftests/bpf: Add bpf_red test Geliang Tang
2022-12-02 14:36 ` selftests/bpf: Add bpf_red test: Tests Results MPTCP CI
2022-12-06 1:13 ` Mat Martineau [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=a65197b3-6504-9b89-315a-76f7b5f92eec@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=geliang.tang@suse.com \
--cc=mptcp@lists.linux.dev \
/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