netdev.vger.kernel.org archive mirror
 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, hideaki.yoshifuji@miraclelinux.com
Subject: [PATCHv2 net-next 0/5] sctp: fully support for dscp and flowlabel per transport
Date: Mon,  2 Jul 2018 18:21:10 +0800	[thread overview]
Message-ID: <cover.1530526661.git.lucien.xin@gmail.com> (raw)

Now dscp and flowlabel are set from sock when sending the packets,
but being multi-homing, sctp also supports for dscp and flowlabel
per transport, which is described in section 8.1.12 in RFC6458.

v1->v2:
  - define ip_queue_xmit as inline in net/ip.h, instead of exporting
    it in Patch 1/5 according to David's suggestion.
  - fix the param len check in sctp_s/getsockopt_peer_addr_params()
    in Patch 3/5 to guarantee that an old app built with old kernel
    headers could work on the newer kernel per Marcelo's point.

Xin Long (5):
  ipv4: add __ip_queue_xmit() that supports tos param
  sctp: add support for dscp and flowlabel per transport
  sctp: add spp_ipv6_flowlabel and spp_dscp for sctp_paddrparams
  sctp: add support for setting flowlabel when adding a transport
  sctp: check for ipv6_pinfo legal sndflow with flowlabel in
    sctp_v6_get_dst

 include/linux/sctp.h       |   7 ++
 include/net/ip.h           |   9 ++-
 include/net/sctp/structs.h |   9 +++
 include/uapi/linux/sctp.h  |   4 +
 net/ipv4/ip_output.c       |   9 ++-
 net/sctp/associola.c       |  15 ++++
 net/sctp/ipv6.c            |  20 ++++-
 net/sctp/protocol.c        |  16 +++-
 net/sctp/socket.c          | 182 +++++++++++++++++++++++++++++++++++++++++++--
 9 files changed, 254 insertions(+), 17 deletions(-)

-- 
2.1.0

             reply	other threads:[~2018-07-02 10:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02 10:21 Xin Long [this message]
2018-07-02 10:21 ` [PATCHv2 net-next 1/5] ipv4: add __ip_queue_xmit() that supports tos param Xin Long
2018-07-02 10:21 ` [PATCHv2 net-next 2/5] sctp: add support for dscp and flowlabel per transport Xin Long
2018-07-02 10:21 ` [PATCHv2 net-next 3/5] sctp: add spp_ipv6_flowlabel and spp_dscp for sctp_paddrparams Xin Long
2018-07-02 10:21 ` [PATCHv2 net-next 4/5] sctp: add support for setting flowlabel when adding a transport Xin Long
2018-07-02 10:21 ` [PATCHv2 net-next 5/5] sctp: check for ipv6_pinfo legal sndflow with flowlabel in sctp_v6_get_dst Xin Long
2018-07-03  1:54 ` [PATCHv2 net-next 0/5] sctp: fully support for dscp and flowlabel per transport Marcelo Ricardo Leitner
2018-07-03 10:50 ` Neil Horman

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.1530526661.git.lucien.xin@gmail.com \
    --to=lucien.xin@gmail.com \
    --cc=davem@davemloft.net \
    --cc=hideaki.yoshifuji@miraclelinux.com \
    --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 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).