From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Ricardo Leitner Subject: Re: [PATCHv2 net-next 0/5] sctp: fully support for dscp and flowlabel per transport Date: Mon, 2 Jul 2018 22:54:51 -0300 Message-ID: <20180703015450.GD26991@localhost.localdomain> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: network dev , linux-sctp@vger.kernel.org, Neil Horman , davem@davemloft.net, hideaki.yoshifuji@miraclelinux.com To: Xin Long Return-path: Received: from mail-qk0-f195.google.com ([209.85.220.195]:36198 "EHLO mail-qk0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752918AbeGCBy4 (ORCPT ); Mon, 2 Jul 2018 21:54:56 -0400 Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: 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