All of lore.kernel.org
 help / color / mirror / Atom feed
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>,
	davem@davemloft.net
Subject: [PATCH net-next 0/3] sctp: add SCTP_ECN_SUPPORTED sockopt
Date: Mon, 26 Aug 2019 08:30:01 +0000	[thread overview]
Message-ID: <cover.1566807985.git.lucien.xin@gmail.com> (raw)

This patchset is to make ecn flag per netns and endpoint and then
add SCTP_ECN_SUPPORTED sockopt, as does for other feature flags.

Xin Long (3):
  sctp: make ecn flag per netns and endpoint
  sctp: allow users to set netns ecn flag with sysctl
  sctp: allow users to set ep ecn flag by sockopt

 include/net/netns/sctp.h   |  3 ++
 include/net/sctp/structs.h |  3 +-
 include/uapi/linux/sctp.h  |  1 +
 net/sctp/endpointola.c     |  1 +
 net/sctp/protocol.c        |  3 ++
 net/sctp/sm_make_chunk.c   | 16 +++++++---
 net/sctp/socket.c          | 73 ++++++++++++++++++++++++++++++++++++++++++++++
 net/sctp/sysctl.c          |  7 +++++
 8 files changed, 102 insertions(+), 5 deletions(-)

-- 
2.1.0

WARNING: multiple messages have this Message-ID (diff)
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>,
	davem@davemloft.net
Subject: [PATCH net-next 0/3] sctp: add SCTP_ECN_SUPPORTED sockopt
Date: Mon, 26 Aug 2019 16:30:01 +0800	[thread overview]
Message-ID: <cover.1566807985.git.lucien.xin@gmail.com> (raw)

This patchset is to make ecn flag per netns and endpoint and then
add SCTP_ECN_SUPPORTED sockopt, as does for other feature flags.

Xin Long (3):
  sctp: make ecn flag per netns and endpoint
  sctp: allow users to set netns ecn flag with sysctl
  sctp: allow users to set ep ecn flag by sockopt

 include/net/netns/sctp.h   |  3 ++
 include/net/sctp/structs.h |  3 +-
 include/uapi/linux/sctp.h  |  1 +
 net/sctp/endpointola.c     |  1 +
 net/sctp/protocol.c        |  3 ++
 net/sctp/sm_make_chunk.c   | 16 +++++++---
 net/sctp/socket.c          | 73 ++++++++++++++++++++++++++++++++++++++++++++++
 net/sctp/sysctl.c          |  7 +++++
 8 files changed, 102 insertions(+), 5 deletions(-)

-- 
2.1.0


             reply	other threads:[~2019-08-26  8:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-26  8:30 Xin Long [this message]
2019-08-26  8:30 ` [PATCH net-next 0/3] sctp: add SCTP_ECN_SUPPORTED sockopt Xin Long
2019-08-26  8:30 ` [PATCH net-next 1/3] sctp: make ecn flag per netns and endpoint Xin Long
2019-08-26  8:30   ` Xin Long
2019-08-26  8:30   ` [PATCH net-next 2/3] sctp: allow users to set netns ecn flag with sysctl Xin Long
2019-08-26  8:30     ` Xin Long
2019-08-26  8:30     ` [PATCH net-next 3/3] sctp: allow users to set ep ecn flag by sockopt Xin Long
2019-08-26  8:30       ` Xin Long
2019-08-26 11:02 ` [PATCH net-next 0/3] sctp: add SCTP_ECN_SUPPORTED sockopt Neil Horman
2019-08-26 11:02   ` Neil Horman
2019-08-28  3:55   ` David Miller
2019-08-28  3:55     ` David Miller

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.1566807985.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 \
    /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.