From: "Nambiar, Amritha" <amritha.nambiar@intel.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
jakub.kicinski@netronome.com, sridhar.samudrala@intel.com,
jhs@mojatatu.com, xiyou.wangcong@gmail.com
Subject: Re: [iproute2 PATCH] tc: flower: Classify packets based port ranges
Date: Thu, 18 Oct 2018 11:25:40 -0700 [thread overview]
Message-ID: <59aaf08b-3da9-2574-2dbd-50a686d6b195@intel.com> (raw)
In-Reply-To: <20181018122136.GB4558@nanopsycho.orion>
On 10/18/2018 5:21 AM, Jiri Pirko wrote:
> Fri, Oct 12, 2018 at 03:54:42PM CEST, amritha.nambiar@intel.com wrote:
>
> [...]
>
>> @@ -1516,6 +1625,22 @@ static int flower_print_opt(struct filter_util *qu, FILE *f,
>> if (nl_type >= 0)
>> flower_print_port("src_port", tb[nl_type]);
>>
>> + if (flower_port_range_attr_type(ip_proto, FLOWER_ENDPOINT_DST, &range)
>> + == 0) {
>> + flower_print_port_range("dst_port_min",
>> + tb[range.min_port_type]);
>> + flower_print_port_range("dst_port_max",
>> + tb[range.max_port_type]);
>
> The input and output of iproute2 utils, tc included should be in sync.
> So you need to print "range x-y" here.
>
Agree, will fix in v2. Thanks!
>
>> + }
>> +
>> + if (flower_port_range_attr_type(ip_proto, FLOWER_ENDPOINT_SRC, &range)
>> + == 0) {
>> + flower_print_port_range("src_port_min",
>> + tb[range.min_port_type]);
>> + flower_print_port_range("src_port_max",
>> + tb[range.max_port_type]);
>> + }
>> +
>> flower_print_tcp_flags("tcp_flags", tb[TCA_FLOWER_KEY_TCP_FLAGS],
>> tb[TCA_FLOWER_KEY_TCP_FLAGS_MASK]);
>>
>>
prev parent reply other threads:[~2018-10-19 2:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 13:54 [iproute2 PATCH] tc: flower: Classify packets based port ranges Amritha Nambiar
2018-10-18 12:21 ` Jiri Pirko
2018-10-18 18:25 ` Nambiar, Amritha [this message]
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=59aaf08b-3da9-2574-2dbd-50a686d6b195@intel.com \
--to=amritha.nambiar@intel.com \
--cc=jakub.kicinski@netronome.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=sridhar.samudrala@intel.com \
--cc=stephen@networkplumber.org \
--cc=xiyou.wangcong@gmail.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