From: roopa <roopa@cumulusnetworks.com>
To: Julian Anastasov <ja@ssi.bg>
Cc: ebiederm@xmission.com, rshearma@brocade.com, tgraf@suug.ch,
davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH net-next RFC v2 2/3] ipv4: add support for light weight tunnel encap attributes
Date: Fri, 19 Jun 2015 07:19:20 -0700 [thread overview]
Message-ID: <558424E8.5090806@cumulusnetworks.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1506190857520.1731@ja.home.ssi.bg>
On 6/18/15, 11:59 PM, Julian Anastasov wrote:
> Hello,
>
> On Thu, 18 Jun 2015, Roopa Prabhu wrote:
>
>> @@ -366,6 +371,7 @@ static inline size_t fib_nlmsg_size(struct fib_info *fi)
>> payload += nla_total_size((RTAX_MAX * nla_total_size(4)));
>>
>> if (fi->fib_nhs) {
>> + size_t nh_encapsize = 0;
> Var not in #ifdef. Any warnings with CONFIG_LWTUNNEL=n?
>
>> /* Also handles the special case fib_nhs == 1 */
>>
>> /* each nexthop is packed in an attribute */
>> @@ -374,8 +380,23 @@ static inline size_t fib_nlmsg_size(struct fib_info *fi)
>> /* may contain flow and gateway attribute */
>> nhsize += 2 * nla_total_size(4);
>>
>> +#ifdef CONFIG_LWTUNNEL
>> + /* grab encap info */
>> + for_nexthops(fi) {
>> + if (nh->nh_lwtstate) {
>> + /* RTA_ENCAP_TYPE */
>> + nh_encapsize += lwtunnel_get_encap_size(
>> + nh->nh_lwtstate);
> New labels not in #ifdef:
Will check and fix all warnings with CONFIG_LWTUNNEL off
>
>> +
>> +err_inval:
>> + ret = -EINVAL;
>> +
>> +errout:
>> + return ret;
>> }
> Some other places may need changes:
>
> - nh_comp: there is logic that decides if same fib_info
> is reused from many fib nodes. There should be check
> if NH matches by nh_lwtstate.
yes, i will add that.
>
> - xfrm4_fill_dst: not sure about this but some fields
> are copied.
>
I have not picked up xfrm4_fill_dst specifically, but this infra is
supposed to be similar to that.
I will look.
Thanks.
next prev parent reply other threads:[~2015-06-19 14:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 4:49 [PATCH net-next RFC v2 2/3] ipv4: add support for light weight tunnel encap attributes Roopa Prabhu
2015-06-19 6:59 ` Julian Anastasov
2015-06-19 14:19 ` roopa [this message]
2015-06-19 14:55 ` Robert Shearman
2015-06-19 15:15 ` roopa
2015-06-19 15:19 ` Robert Shearman
2015-06-19 15:28 ` roopa
2015-06-19 17:17 ` Robert Shearman
2015-06-19 18:42 ` roopa
2015-06-21 20:20 ` Thomas Graf
2015-06-22 2:30 ` roopa
2015-07-03 10:00 ` Summary lightweight tunnel discussion at NFWS Thomas Graf
2015-07-05 6:21 ` roopa
2015-07-06 13:03 ` Thomas Graf
2015-07-06 15:24 ` roopa
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=558424E8.5090806@cumulusnetworks.com \
--to=roopa@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=ja@ssi.bg \
--cc=netdev@vger.kernel.org \
--cc=rshearma@brocade.com \
--cc=tgraf@suug.ch \
/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).