From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>, linux-sctp@vger.kernel.org
Cc: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Neil Horman <nhorman@tuxdriver.com>,
Vlad Yasevich <vyasevich@gmail.com>,
davem@davemloft.net
Subject: [PATCHv2 net-next 0/3] sctp: prepare asoc stream for stream reconf
Date: Tue, 03 Jan 2017 05:59:45 +0000 [thread overview]
Message-ID: <cover.1483422833.git.lucien.xin@gmail.com> (raw)
sctp stream reconf, described in RFC 6525, needs a structure to
save per stream information in assoc, like stream state.
In the future, sctp stream scheduler also needs it to save some
stream scheduler params and queues.
This patchset is to prepare the stream array in assoc for stream
reconf.
v1->v2:
put these patches into a smaller group.
Xin Long (3):
sctp: add stream arrays in asoc
sctp: replace ssnmap with asoc stream arrays
sctp: remove asoc ssnmap and ssnmap.c
include/net/sctp/sctp.h | 1 -
include/net/sctp/structs.h | 70 +++++++++----------------
net/sctp/Makefile | 3 +-
net/sctp/associola.c | 23 ++++++---
net/sctp/objcnt.c | 2 -
net/sctp/sm_make_chunk.c | 24 ++++++---
net/sctp/sm_statefuns.c | 3 +-
net/sctp/ssnmap.c | 125 ---------------------------------------------
net/sctp/ulpqueue.c | 33 ++++--------
9 files changed, 69 insertions(+), 215 deletions(-)
delete mode 100644 net/sctp/ssnmap.c
--
2.1.0
next reply other threads:[~2017-01-03 5:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 5:59 Xin Long [this message]
2017-01-03 5:59 ` [PATCHv2 net-next 1/3] sctp: add stream arrays in asoc Xin Long
2017-01-03 5:59 ` [PATCHv2 net-next 2/3] sctp: replace ssnmap with asoc stream arrays Xin Long
2017-01-03 5:59 ` [PATCHv2 net-next 3/3] sctp: remove asoc ssnmap and ssnmap.c Xin Long
2017-01-04 13:39 ` [PATCHv2 net-next 1/3] sctp: add stream arrays in asoc Marcelo Ricardo Leitner
2017-01-06 13:57 ` Xin Long
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=cover.1483422833.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=vyasevich@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).