From: Paolo Abeni <pabeni@redhat.com>
To: Geliang Tang <geliangtang@gmail.com>, mptcp@lists.linux.dev
Cc: Geliang Tang <geliangtang@xiaomi.com>
Subject: Re: [PATCH RFC mptcp-next 2/4] mptcp: add struct mptcp_sched_ops
Date: Tue, 07 Sep 2021 13:04:52 +0200 [thread overview]
Message-ID: <48bc68806ca2cbcb33dffddd2f450a541b8f6500.camel@redhat.com> (raw)
In-Reply-To: <4089672c8557e031d38306ef49e26e9902e7db57.1631011068.git.geliangtang@xiaomi.com>
On Tue, 2021-09-07 at 18:41 +0800, Geliang Tang wrote:
> From: Geliang Tang <geliangtang@xiaomi.com>
>
> This patch added struct mptcp_sched_ops. And define the scheduler
> init, register and find functions.
>
> Signed-off-by: Geliang Tang <geliangtang@xiaomi.com>
> ---
> net/mptcp/protocol.c | 60 +++++++++++++++++++++++++++++++++++++++++---
> net/mptcp/protocol.h | 8 ++++++
> 2 files changed, 65 insertions(+), 3 deletions(-)
>
> diff --git a/net/mptcp/protocol.c b/net/mptcp/protocol.c
> index 2a525c7ae920..ab72a3950f2b 100644
> --- a/net/mptcp/protocol.c
> +++ b/net/mptcp/protocol.c
> @@ -1515,6 +1515,58 @@ static struct sock *mptcp_subflow_get_send(struct mptcp_sock *msk)
> return NULL;
> }
>
> +static struct mptcp_sched_ops mptcp_sched_default = {
> + .get_subflow = mptcp_subflow_get_send,
> + .name = "default",
> + .owner = THIS_MODULE,
> +};
> +
> +static DEFINE_SPINLOCK(mptcp_sched_list_lock);
> +static LIST_HEAD(mptcp_sched_list);
> +
> +static struct mptcp_sched_ops *mptcp_sched_find(const char *name)
> +{
> + struct mptcp_sched_ops *ops;
> +
> + list_for_each_entry_rcu(ops, &mptcp_sched_list, list) {
> + if (!strcmp(ops->name, name))
> + return ops;
> + }
> +
> + return NULL;
> +}
> +
> +static int mptcp_register_scheduler(struct mptcp_sched_ops *sched)
> +{
> + int ret = 0;
> +
> + if (!sched->get_subflow)
> + return -EINVAL;
> +
> + spin_lock(&mptcp_sched_list_lock);
> + if (mptcp_sched_find(sched->name)) {
> + pr_debug("%s already registered", sched->name);
> + ret = -EEXIST;
> + } else {
> + list_add_tail_rcu(&sched->list, &mptcp_sched_list);
> + pr_debug("%s registered", sched->name);
> + }
> + spin_unlock(&mptcp_sched_list_lock);
> + return 0;
> +}
> +
> +static void mptcp_sched_data_init(struct mptcp_sock *msk)
> +{
> + struct net *net = sock_net((struct sock *)msk);
> +
> + msk->sched = mptcp_sched_find(mptcp_get_scheduler(net));
> +}
> +
> +static void mptcp_sched_init(void)
> +{
> + mptcp_register_scheduler(&mptcp_sched_default);
> +}
> +
I think it would be nice keeping this infrastructure in a separate
file, but I have no strong opinion on it.
> static void mptcp_push_release(struct sock *sk, struct sock *ssk,
> struct mptcp_sendmsg_info *info)
> {
> @@ -1567,7 +1619,7 @@ void __mptcp_push_pending(struct sock *sk, unsigned int flags)
>
> prev_ssk = ssk;
> mptcp_flush_join_list(msk);
> - ssk = mptcp_subflow_get_send(msk);
> + ssk = msk->sched->get_subflow(msk);
uhm... it would be nice to avoid the indirect call, but I don't see any
solution other then IDC wrapper usage
(see linux/indirect_call_wrapper.h)
> /* First check. If the ssk has changed since
> * the last round, release prev_ssk
> @@ -1634,7 +1686,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_sk(sk)->sched->get_subflow(mptcp_sk(sk));
> if (!xmit_ssk)
> goto out;
> if (xmit_ssk != ssk) {
> @@ -2534,6 +2586,7 @@ static int __mptcp_init_sock(struct sock *sk)
> msk->recovery = false;
>
> mptcp_pm_data_init(msk);
> + mptcp_sched_data_init(msk);
>
> /* re-use the csk retrans timer for MPTCP-level retrans */
> timer_setup(&msk->sk.icsk_retransmit_timer, mptcp_retransmit_timer, 0);
I think we should do the lookup in mptcp_init_sock(), and copy the
scheduler from the parent in mptcp_sk_clone().
Cheers,
Paolo
next prev parent reply other threads:[~2021-09-07 11:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 10:41 [PATCH RFC mptcp-next 0/4] round-robin packet scheduler support Geliang Tang
2021-09-07 10:41 ` [PATCH RFC mptcp-next 1/4] mptcp: add a new sysctl scheduler Geliang Tang
2021-09-07 10:59 ` Paolo Abeni
2021-09-07 10:41 ` [PATCH RFC mptcp-next 2/4] mptcp: add struct mptcp_sched_ops Geliang Tang
2021-09-07 11:04 ` Paolo Abeni [this message]
2021-09-07 10:41 ` [PATCH RFC mptcp-next 3/4] mptcp: round-robin packet scheduler support Geliang Tang
2021-09-07 11:16 ` Paolo Abeni
2021-09-09 0:18 ` Mat Martineau
2021-09-07 10:41 ` [PATCH RFC mptcp-next 4/4] selftests: mptcp: add round-robin testcase Geliang Tang
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=48bc68806ca2cbcb33dffddd2f450a541b8f6500.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=geliangtang@gmail.com \
--cc=geliangtang@xiaomi.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