From: Patrick McHardy <kaber@trash.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: gre: minor cleanups in netlink interface
Date: Sat, 11 Oct 2008 17:39:36 +0200 [thread overview]
Message-ID: <48F0C8B8.7010400@trash.net> (raw)
In-Reply-To: <20081011151820.GB7520@gondor.apana.org.au>
Herbert Xu wrote:
> On Sat, Oct 11, 2008 at 04:45:48PM +0200, Patrick McHardy wrote:
>> Its actually also what defines the difference between using
>> NLM_F_REPLACE (ip link replace) and no flags (ip link change).
>> The former replaces the replaces the object, the later changes
>> an existing object.
>
> That wasn't the case historically. For routing NLM_F_REPLACE
> had a real meaning because you can have routes that differ only
> by scope. So if you considered routes that are otherwise the
> same to be duplicate routes, then NLM_F_REPLACE tells you whether
> you're allowed to create a new route or you must modify one
> of the existing ones. Of course completely duplicate routes
> where everything is equal is not allowed.
Interesting, I wasn't aware of that.
> Of course NLM_F_REPLACE has since been seconded for other purposes
> so I suppose it can mean whatever you want for rtnl link :)
It actually not supported currently because replacement of links
(while keeping routes etc.) would be highly complicated.
next prev parent reply other threads:[~2008-10-11 15:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 16:04 gre: minor cleanups in netlink interface Patrick McHardy
2008-10-10 19:11 ` David Miller
2008-10-11 10:39 ` Herbert Xu
2008-10-11 12:43 ` Herbert Xu
2008-10-11 19:20 ` David Miller
2008-10-11 14:43 ` Patrick McHardy
2008-10-11 14:45 ` Patrick McHardy
2008-10-11 15:18 ` Herbert Xu
2008-10-11 15:39 ` Patrick McHardy [this message]
2008-10-11 15:03 ` Herbert Xu
2008-10-11 15:15 ` Patrick McHardy
2008-10-11 15:26 ` Herbert Xu
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=48F0C8B8.7010400@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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).