From: Stephen Hemminger <stephen@networkplumber.org>
To: David Ahern <dsa@cumulusnetworks.com>
Cc: netdev@vger.kernel.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
roopa <roopa@cumulusnetworks.com>
Subject: Re: [PATCH net-next iproute2] ip: increase number of MPLS labels
Date: Mon, 1 May 2017 09:15:40 -0700 [thread overview]
Message-ID: <20170501091540.13f57676@xeon-e3> (raw)
In-Reply-To: <ddb54ca8-d7df-3446-3929-5f0116286c80@cumulusnetworks.com>
On Sun, 30 Apr 2017 17:42:15 -0600
David Ahern <dsa@cumulusnetworks.com> wrote:
> On 4/30/17 12:04 AM, Stephen Hemminger wrote:
> > On Sat, 29 Apr 2017 20:48:50 -0700
> > David Ahern <dsa@cumulusnetworks.com> wrote:
> >
> >> Kernel now supports more than 2 labels. Increase ip to
> >> handle up to 16 labels.
> >>
> >> Signed-off-by: David Ahern <dsa@cumulusnetworks.com>
> >> ---
> >> include/utils.h | 8 ++++----
> >> lib/utils.c | 2 +-
> >> 2 files changed, 5 insertions(+), 5 deletions(-)
> >>
> >> diff --git a/include/utils.h b/include/utils.h
> >> index 8c12e1e2a60c..a69e176c260d 100644
> >> --- a/include/utils.h
> >> +++ b/include/utils.h
> >> @@ -54,6 +54,9 @@ void incomplete_command(void) __attribute__((noreturn));
> >> #define NEXT_ARG_FWD() do { argv++; argc--; } while(0)
> >> #define PREV_ARG() do { argv--; argc++; } while(0)
> >>
> >> +/* Maximum number of labels the mpls helpers support */
> >> +#define MPLS_MAX_LABELS 16
> >> +
> >
> > Why is the kernel limit not in include/uapi/ header file?
> >
>
> I believe Eric had reasons, but not sure why.
I just don't want iproute2 utilities chasing kernel values.
Would prefer either make utilities take any size, or inherit maximum from kernel headers.
next prev parent reply other threads:[~2017-05-01 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 3:48 [PATCH net-next iproute2] ip: increase number of MPLS labels David Ahern
2017-04-30 6:04 ` Stephen Hemminger
2017-04-30 23:42 ` David Ahern
2017-05-01 16:15 ` Stephen Hemminger [this message]
2017-05-01 21:03 ` Eric W. Biederman
2017-05-01 21:22 ` David Ahern
2017-05-01 21:57 ` Eric W. Biederman
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=20170501091540.13f57676@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dsa@cumulusnetworks.com \
--cc=ebiederm@xmission.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.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;
as well as URLs for NNTP newsgroup(s).