From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Xin Long <lucien.xin@gmail.com>
Cc: network dev <netdev@vger.kernel.org>,
linux-sctp@vger.kernel.org, Neil Horman <nhorman@tuxdriver.com>,
davem@davemloft.net, hideaki.yoshifuji@miraclelinux.com
Subject: Re: [PATCHv2 net-next 0/5] sctp: fully support for dscp and flowlabel per transport
Date: Tue, 03 Jul 2018 01:54:51 +0000 [thread overview]
Message-ID: <20180703015450.GD26991@localhost.localdomain> (raw)
In-Reply-To: <cover.1530526661.git.lucien.xin@gmail.com>
On Mon, Jul 02, 2018 at 06:21:10PM +0800, Xin Long wrote:
> 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
Series
Acked-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
next prev parent reply other threads:[~2018-07-03 1:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 10:21 [PATCHv2 net-next 0/5] sctp: fully support for dscp and flowlabel per transport Xin Long
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 ` Marcelo Ricardo Leitner [this message]
2018-07-03 10:50 ` [PATCHv2 net-next 0/5] sctp: fully support for dscp and flowlabel per transport 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=20180703015450.GD26991@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=davem@davemloft.net \
--cc=hideaki.yoshifuji@miraclelinux.com \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@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).