From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] ipv6: export IP6_RT_PRIO_* to userland
Date: Mon, 05 Nov 2012 18:22:39 +0100 [thread overview]
Message-ID: <5097F5DF.7040507@6wind.com> (raw)
In-Reply-To: <20121105.120017.1189906314924845791.davem@davemloft.net>
Le 05/11/2012 18:00, David Miller a écrit :
> From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
> Date: Mon, 5 Nov 2012 16:28:18 +0100
>
>> The kernel uses some default metric when routes are managed. For example, a
>> static route added with a metric set to 0 is inserted in the kernel with
>> metric 1024 (IP6_RT_PRIO_USER).
>> It is useful for routing daemons to know these values, to be able to set routes
>> without interfering with what the kernel does.
>>
>> Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
>
> But these belong in the libc headers anyways.
>
> If we haven't provided them for so long, there's no real value of
> adding them now.
>
But how can a daemon know which default values are used? If it wants to add a
route with metric = default + x, it should first add it with metric = 0, check
the result and then change the metric.
next prev parent reply other threads:[~2012-11-05 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 15:28 [PATCH net-next] ipv6: export IP6_RT_PRIO_* to userland Nicolas Dichtel
2012-11-05 17:00 ` David Miller
2012-11-05 17:22 ` Nicolas Dichtel [this message]
2012-11-05 17:43 ` David Miller
2012-11-05 19:24 ` Nicolas Dichtel
2012-11-09 9:43 ` Nicolas Dichtel
2012-11-09 19:05 ` David Miller
2012-11-16 6:48 ` David Miller
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=5097F5DF.7040507@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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).