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/5] sctp: fully support for dscp and flowlabel per transport
Date: Mon, 25 Jun 2018 10:14:32 +0800	[thread overview]
Message-ID: <cover.1529892764.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.

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           |   2 +
 include/net/sctp/structs.h |   9 +++
 include/uapi/linux/sctp.h  |   4 ++
 net/ipv4/ip_output.c       |  13 +++-
 net/sctp/associola.c       |  15 +++++
 net/sctp/ipv6.c            |  20 +++++-
 net/sctp/protocol.c        |  16 +++--
 net/sctp/socket.c          | 157 +++++++++++++++++++++++++++++++++++++++++++++
 9 files changed, 234 insertions(+), 9 deletions(-)

-- 
2.1.0

             reply	other threads:[~2018-06-25  2:14 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-25  2:14 Xin Long [this message]
2018-06-25  2:14 ` [PATCH net-next 1/5] ipv4: add __ip_queue_xmit() that supports tos param Xin Long
2018-06-25  2:14   ` [PATCH net-next 2/5] sctp: add support for dscp and flowlabel per transport Xin Long
2018-06-25  2:14     ` Xin Long
2018-06-25  2:14     ` [PATCH net-next 3/5] sctp: add spp_ipv6_flowlabel and spp_dscp for sctp_paddrparams Xin Long
2018-06-25  2:14       ` Xin Long
2018-06-25  7:31       ` David Miller
2018-06-25  7:31         ` David Miller
2018-06-25 11:28         ` Neil Horman
2018-06-25 11:28           ` Neil Horman
2018-06-25 13:03           ` Marcelo Ricardo Leitner
2018-06-25 13:03             ` Marcelo Ricardo Leitner
2018-06-25 16:12             ` 吉藤英明
2018-06-25 16:12               ` 吉藤英明
2018-06-25 16:31               ` Marcelo Ricardo Leitner
2018-06-25 16:31                 ` Marcelo Ricardo Leitner
2018-06-26  4:33                 ` Xin Long
2018-06-26  4:33                   ` Xin Long
2018-06-26 12:02                   ` 吉藤英明
2018-06-26 12:02                     ` 吉藤英明
2018-06-28  6:40                     ` Xin Long
2018-06-28  6:40                       ` Xin Long
2018-06-30  8:15                       ` 吉藤英明
2018-06-30  8:15                         ` 吉藤英明
2018-06-25  7:26   ` [PATCH net-next 1/5] ipv4: add __ip_queue_xmit() that supports tos param David Miller
2018-06-25 11:13     ` Neil Horman
2018-06-26  4:38       ` Xin Long
2018-06-25  2:14 ` [PATCH net-next 4/5] sctp: add support for setting flowlabel when adding a transport Xin Long
2018-06-25  2:14 ` [PATCH net-next 5/5] sctp: check for ipv6_pinfo legal sndflow with flowlabel in sctp_v6_get_dst 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.1529892764.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.