From: Shan Wei <shanwei@cn.fujitsu.com>
To: Yaogong Wang <ywang15@ncsu.edu>
Cc: linux-sctp@vger.kernel.org,
Vlad Yasevich <vladislav.yasevich@hp.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 3/5] sctp: extend socket API for sched configuration
Date: Wed, 13 Oct 2010 08:31:59 +0000 [thread overview]
Message-ID: <4CB56E7F.3030908@cn.fujitsu.com> (raw)
In-Reply-To: <AANLkTimEQkDpWorCF4HUq6N-xAnFz4xE89osAtcJY_Mn@mail.gmail.com>
Yaogong Wang wrote, at 09/12/2010 09:13 AM:
> Augment SCTP socket API with a new socket option SCTP_SCHED
> to choose and configure multistream scheduling algorithm.
>
> Signed-off-by: Yaogong Wang <ywang15@ncsu.edu>
> ---
> include/net/sctp/structs.h | 4 ++
> include/net/sctp/user.h | 19 ++++++++++
> net/sctp/outqueue.c | 4 ++
> net/sctp/sm_sideeffect.c | 45 +++++++++++++++++++++++--
> net/sctp/socket.c | 80 ++++++++++++++++++++++++++++++++++++++++++++
> 5 files changed, 149 insertions(+), 3 deletions(-)
>
> diff --git a/include/net/sctp/structs.h b/include/net/sctp/structs.h
> index 52af764..1a76417 100644
> --- a/include/net/sctp/structs.h
> +++ b/include/net/sctp/structs.h
> @@ -333,6 +333,8 @@ struct sctp_sock {
>
> /* Multistream scheduling */
> const struct sctp_sched_ops *sched_ops;
> + __u16 sched_config_len;
> + void *sched_config;
>
> struct sctp_initmsg initmsg;
> struct sctp_rtoinfo rtoinfo;
> @@ -1173,6 +1175,8 @@ struct sctp_outq {
>
> /* Multistream scheduling */
> const struct sctp_sched_ops *sched_ops;
> + __u16 sched_config_len;
> + void *sched_config;
Why did you take these two fields into sctp_sock and sctp_outq?
These two fields between sctp_sock and sctp_outq has same role,
we can only defined in one place.
How about using sctp_sk(sctp_outq->asoc->base.sk) to access these two
fields?
--
Best Regards
-----
Shan Wei
WARNING: multiple messages have this Message-ID (diff)
From: Shan Wei <shanwei@cn.fujitsu.com>
To: Yaogong Wang <ywang15@ncsu.edu>
Cc: linux-sctp@vger.kernel.org,
Vlad Yasevich <vladislav.yasevich@hp.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 3/5] sctp: extend socket API for sched configuration
Date: Wed, 13 Oct 2010 16:31:59 +0800 [thread overview]
Message-ID: <4CB56E7F.3030908@cn.fujitsu.com> (raw)
In-Reply-To: <AANLkTimEQkDpWorCF4HUq6N-xAnFz4xE89osAtcJY_Mn@mail.gmail.com>
Yaogong Wang wrote, at 09/12/2010 09:13 AM:
> Augment SCTP socket API with a new socket option SCTP_SCHED
> to choose and configure multistream scheduling algorithm.
>
> Signed-off-by: Yaogong Wang <ywang15@ncsu.edu>
> ---
> include/net/sctp/structs.h | 4 ++
> include/net/sctp/user.h | 19 ++++++++++
> net/sctp/outqueue.c | 4 ++
> net/sctp/sm_sideeffect.c | 45 +++++++++++++++++++++++--
> net/sctp/socket.c | 80 ++++++++++++++++++++++++++++++++++++++++++++
> 5 files changed, 149 insertions(+), 3 deletions(-)
>
> diff --git a/include/net/sctp/structs.h b/include/net/sctp/structs.h
> index 52af764..1a76417 100644
> --- a/include/net/sctp/structs.h
> +++ b/include/net/sctp/structs.h
> @@ -333,6 +333,8 @@ struct sctp_sock {
>
> /* Multistream scheduling */
> const struct sctp_sched_ops *sched_ops;
> + __u16 sched_config_len;
> + void *sched_config;
>
> struct sctp_initmsg initmsg;
> struct sctp_rtoinfo rtoinfo;
> @@ -1173,6 +1175,8 @@ struct sctp_outq {
>
> /* Multistream scheduling */
> const struct sctp_sched_ops *sched_ops;
> + __u16 sched_config_len;
> + void *sched_config;
Why did you take these two fields into sctp_sock and sctp_outq?
These two fields between sctp_sock and sctp_outq has same role,
we can only defined in one place.
How about using sctp_sk(sctp_outq->asoc->base.sk) to access these two
fields?
--
Best Regards
-----
Shan Wei
next prev parent reply other threads:[~2010-10-13 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-12 1:13 [PATCHv2 3/5] sctp: extend socket API for sched configuration Yaogong Wang
2010-09-12 1:13 ` Yaogong Wang
2010-10-13 8:31 ` Shan Wei [this message]
2010-10-13 8:31 ` Shan Wei
2010-10-14 17:41 ` Yaogong Wang
2010-10-14 17:41 ` Yaogong Wang
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=4CB56E7F.3030908@cn.fujitsu.com \
--to=shanwei@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=vladislav.yasevich@hp.com \
--cc=ywang15@ncsu.edu \
/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.