From: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
To: David Ahern <dsahern@gmail.com>
Cc: Lorenzo Colitti <lorenzo@google.com>,
netdev@vger.kernel.org,
Stephen Hemminger <stephen@networkplumber.org>,
Steffen Klassert <steffen.klassert@secunet.com>
Subject: Re: [PATCH iproute2-next v2] ip-xfrm: Add support for OUTPUT_MARK
Date: Wed, 13 Jun 2018 23:09:58 -0600 [thread overview]
Message-ID: <b35396f04f5e7209c18cf3cd27ef42e8@codeaurora.org> (raw)
In-Reply-To: <107348e5-3035-8d07-59c0-95a84c4f8222@gmail.com>
> any reason to put output-mark on its own line? Why not
> mark 0x10000/0x3ffff output-mark 0x20000
>
Hi David
I will move it to the same line in v3.
> is the documentation clear on the difference between mark and
> output-mark?
Lorenzo has described the differences in detail in the kernel commit I
had listed in the commit text of this patch. Pasting from there -
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.
The use of a separate mark provides additional flexibility. For
example:
- A packet subject to two transforms (e.g., transport mode inside
tunnel mode) can have two different output marks applied to it,
one for the transport mode SA and one for the tunnel mode SA.
- On a system where socket marks determine routing, the packets
emitted by an IPsec tunnel can be routed based on a mark that
is determined by the tunnel, not by the marks of the
unencrypted packets.
- Support for setting the output marks can be introduced without
breaking any existing setups that employ both mark-based
routing and xfrm tunnel mode. Simply changing the code to use
the xfrm mark for routing output packets could xfrm mark could
change behaviour in a way that breaks these setups.
>
>>
>>> @@ -61,6 +61,7 @@ static void usage(void)
>>> fprintf(stderr, " [ flag FLAG-LIST ] [ sel SELECTOR ]
>>> [ LIMIT-LIST ] [ encap ENCAP ]\n");
>>> fprintf(stderr, " [ coa ADDR[/PLEN] ] [ ctx CTX ] [
>>> extra-flag EXTRA-FLAG-LIST ]\n");
>>> fprintf(stderr, " [ offload [dev DEV] dir DIR ]\n");
>>> + fprintf(stderr, " [ output-mark OUTPUT-MARK]\n");
>>
>> Nit: I think you want a space between OUTPUT-MARK and ].
>
> yes.
>
I will update this as well.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2018-06-14 5:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 18:48 [PATCH iproute2-next v2] ip-xfrm: Add support for OUTPUT_MARK Subash Abhinov Kasiviswanathan
2018-06-13 3:14 ` Lorenzo Colitti
2018-06-13 4:24 ` Stephen Hemminger
2018-06-14 3:39 ` David Ahern
2018-06-14 5:09 ` Subash Abhinov Kasiviswanathan [this message]
2018-06-14 16:29 ` David Ahern
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=b35396f04f5e7209c18cf3cd27ef42e8@codeaurora.org \
--to=subashab@codeaurora.org \
--cc=dsahern@gmail.com \
--cc=lorenzo@google.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=stephen@networkplumber.org \
/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).