From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Ahern Subject: Re: [PATCH iproute2-next v2] ip-xfrm: Add support for OUTPUT_MARK Date: Thu, 14 Jun 2018 10:29:11 -0600 Message-ID: <0d25ad24-b260-1798-a370-c163b068532e@gmail.com> References: <1528829293-23222-1-git-send-email-subashab@codeaurora.org> <107348e5-3035-8d07-59c0-95a84c4f8222@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: Lorenzo Colitti , netdev@vger.kernel.org, Stephen Hemminger , Steffen Klassert To: Subash Abhinov Kasiviswanathan Return-path: Received: from mail-pf0-f173.google.com ([209.85.192.173]:36794 "EHLO mail-pf0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755220AbeFNQ3O (ORCPT ); Thu, 14 Jun 2018 12:29:14 -0400 Received: by mail-pf0-f173.google.com with SMTP id a12-v6so3505568pfi.3 for ; Thu, 14 Jun 2018 09:29:14 -0700 (PDT) In-Reply-To: Content-Language: en-US Sender: netdev-owner@vger.kernel.org List-ID: On 6/13/18 11:09 PM, Subash Abhinov Kasiviswanathan wrote: > The output mark differs from the existing xfrm mark in two ways: > > 1. The xfrm mark is used to match xfrm policies and states, while >    the xfrm output mark is used to set the mark (and influence >    the routing) of the packets emitted by those states. > 2. The existing mark is constrained to be a subset of the bits of >    the originating socket or transformed packet, but the output >    mark is arbitrary and depends only on the state. make sure the man page update contains the description of the 2 marks and why they are used. Thanks,