All of lore.kernel.org
 help / color / mirror / Atom feed
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 v11 5/8] mptcp: add get_subflow wrapper
Date: Fri, 8 Apr 2022 17:03:59 -0700 (PDT)	[thread overview]
Message-ID: <f975ec8e-d53e-6b29-37fc-2c302e5f9ff@linux.intel.com> (raw)
In-Reply-To: <752c5475b78dc8408b2f0dc6274b35dff0a08710.1649432004.git.geliang.tang@suse.com>

On Fri, 8 Apr 2022, Geliang Tang wrote:

> This patch defines a new wrapper mptcp_sched_get_subflow(), invoke
> get_subflow() of msk->sched in it. Use the wrapper instead of using
> mptcp_subflow_get_send() directly.
>
> Signed-off-by: Geliang Tang <geliang.tang@suse.com>
> ---
> net/mptcp/protocol.c | 8 ++++----
> net/mptcp/protocol.h | 6 ++++++
> 2 files changed, 10 insertions(+), 4 deletions(-)
>
> diff --git a/net/mptcp/protocol.c b/net/mptcp/protocol.c
> index 1153bddb92a6..785c428f87ea 100644
> --- a/net/mptcp/protocol.c
> +++ b/net/mptcp/protocol.c
> @@ -1567,7 +1567,7 @@ void __mptcp_push_pending(struct sock *sk, unsigned int flags)
> 			int ret = 0;
>
> 			prev_ssk = ssk;
> -			ssk = mptcp_subflow_get_send(msk);
> +			ssk = mptcp_sched_get_subflow(msk, false);
>
> 			/* First check. If the ssk has changed since
> 			 * the last round, release prev_ssk
> @@ -1636,7 +1636,7 @@ static void __mptcp_subflow_push_pending(struct sock *sk, struct sock *ssk)
> 			 * check for a different subflow usage only after
> 			 * spooling the first chunk of data
> 			 */
> -			xmit_ssk = first ? ssk : mptcp_subflow_get_send(mptcp_sk(sk));
> +			xmit_ssk = first ? ssk : mptcp_sched_get_subflow(mptcp_sk(sk), false);
> 			if (!xmit_ssk)
> 				goto out;
> 			if (xmit_ssk != ssk) {
> @@ -2481,7 +2481,7 @@ static void __mptcp_retrans(struct sock *sk)
> 	mptcp_clean_una_wakeup(sk);
>
> 	/* first check ssk: need to kick "stale" logic */
> -	ssk = mptcp_subflow_get_retrans(msk);
> +	ssk = mptcp_sched_get_subflow(msk, true);
> 	dfrag = mptcp_rtx_head(sk);
> 	if (!dfrag) {
> 		if (mptcp_data_fin_enabled(msk)) {
> @@ -3145,7 +3145,7 @@ void __mptcp_check_push(struct sock *sk, struct sock *ssk)
> 		return;
>
> 	if (!sock_owned_by_user(sk)) {
> -		struct sock *xmit_ssk = mptcp_subflow_get_send(mptcp_sk(sk));
> +		struct sock *xmit_ssk = mptcp_sched_get_subflow(mptcp_sk(sk), false);
>
> 		if (xmit_ssk == ssk)
> 			__mptcp_subflow_push_pending(sk, ssk);
> diff --git a/net/mptcp/protocol.h b/net/mptcp/protocol.h
> index 2b3143045f89..a58c5c84e72b 100644
> --- a/net/mptcp/protocol.h
> +++ b/net/mptcp/protocol.h
> @@ -619,6 +619,12 @@ int mptcp_init_sched(struct mptcp_sock *msk,
> 		     struct mptcp_sched_ops *sched);
> void mptcp_release_sched(struct mptcp_sock *msk);
>
> +static inline struct sock *mptcp_sched_get_subflow(struct mptcp_sock *msk, bool retrans)
> +{
> +	return INDIRECT_CALL_INET_1(msk->sched->get_subflow,
> +				    mptcp_get_subflow_default, msk, retrans);
> +}

Thanks, this works for handling retransmission.

I'd still like to get some community input on the "redundant scheduler" 
use case and allowing simultaneous transmission on multiple subflows 
before we merge these changes to the export branch. Since the APIs for BPF 
are userspace-visible, that's important to sort out. The transmit and 
retransmit code would need big enough changes that it might be good to 
discuss and agree on the requirements first.

> +
> static inline bool __mptcp_subflow_active(struct mptcp_subflow_context *subflow)
> {
> 	struct sock *ssk = mptcp_subflow_tcp_sock(subflow);
> -- 
> 2.34.1
>
>
>

--
Mat Martineau
Intel

  reply	other threads:[~2022-04-09  0:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 15:37 [PATCH mptcp-next v11 0/8] BPF packet scheduler Geliang Tang
2022-04-08 15:37 ` [PATCH mptcp-next v11 1/8] mptcp: add struct mptcp_sched_ops Geliang Tang
2022-04-08 15:37 ` [PATCH mptcp-next v11 2/8] mptcp: register default scheduler Geliang Tang
2022-04-08 15:38 ` [PATCH mptcp-next v11 3/8] mptcp: add a new sysctl scheduler Geliang Tang
2022-04-08 15:38 ` [PATCH mptcp-next v11 4/8] mptcp: add sched in mptcp_sock Geliang Tang
2022-04-08 15:38 ` [PATCH mptcp-next v11 5/8] mptcp: add get_subflow wrapper Geliang Tang
2022-04-09  0:03   ` Mat Martineau [this message]
2022-04-08 15:38 ` [PATCH mptcp-next v11 6/8] mptcp: add bpf_mptcp_sched_ops Geliang Tang
2022-04-08 15:38 ` [PATCH mptcp-next v11 7/8] selftests: bpf: add bpf_first scheduler Geliang Tang
2022-04-08 15:38 ` [PATCH mptcp-next v11 8/8] selftests: bpf: add bpf_first test Geliang Tang
2022-04-08 18:44   ` selftests: bpf: add bpf_first test: Tests Results MPTCP CI
2022-04-20  0:12 ` [PATCH mptcp-next v11 0/8] BPF packet scheduler Mat Martineau

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=f975ec8e-d53e-6b29-37fc-2c302e5f9ff@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.