From: Roopa Prabhu <roopa@cumulusnetworks.com>
To: Magnus Bergroth <bergroth@nordu.net>
Cc: netdev@vger.kernel.org, Robert Shearman <rshearma@brocade.com>,
"ebiederm@xmission.com" <ebiederm@xmission.com>
Subject: Re: iproute2 mpls max labels
Date: Sat, 23 Jul 2016 16:04:40 -0700 [thread overview]
Message-ID: <5793F808.6090309@cumulusnetworks.com> (raw)
In-Reply-To: <579125CB.3030201@nordu.net>
On 7/21/16, 12:43 PM, Magnus Bergroth wrote:
>
>> Roopa Prabhu <mailto:roopa@cumulusnetworks.com>
>> 21 juli 2016 20:53
>> I did not realize it is hardcoded to 8 in iproute2. Because kernel has
>> a hard coded limit of
>> 2.
>> I think we need to fix it in a few places:
>> a) we should move the kernel #define to a uapi header file which
>> iproute2 can use
>> b) there has been a general ask to bump the kernel MAX_LABELS from 2
>> and I don't see
>> a problem with it yet. so, we could bump it to 8.
>>
>> Were you planning to post patches for one or both of the above ?.
>>
>> I can post them too. Let me know.
> I would be happy if you could post them both as I very new to the kernel
> development and I'm not entirely sure how to do it in the right way.
>
ok, sure, will fix it.
thanks,
Roopa
next prev parent reply other threads:[~2016-07-23 23:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-16 18:24 iproute2 mpls max labels Magnus Bergroth
2016-07-21 18:53 ` Roopa Prabhu
2016-07-21 19:43 ` Magnus Bergroth
2016-07-23 23:04 ` Roopa Prabhu [this message]
2016-07-21 20:00 ` Eric W. Biederman
2016-07-21 21:08 ` Magnus Bergroth
2016-07-22 19:24 ` Eric W. Biederman
2016-07-22 6:16 ` Roopa Prabhu
2016-07-22 19:20 ` Eric W. Biederman
2016-07-23 23:03 ` Roopa Prabhu
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=5793F808.6090309@cumulusnetworks.com \
--to=roopa@cumulusnetworks.com \
--cc=bergroth@nordu.net \
--cc=ebiederm@xmission.com \
--cc=netdev@vger.kernel.org \
--cc=rshearma@brocade.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.