From: "Stian Skjelstad" <stian@nixia.no>
To: "Denys Fedoryshchenko" <denys@visp.net.lb>
Cc: "Stephen Hemminger" <shemminger@vyatta.com>,
"Stian Skjelstad" <stian@nixia.no>,
eric.dumazet@gmail.com, stephen.hemminger@vyatta.com,
netdev@vger.kernel.org
Subject: Re: Netlink, route monitoring, RTM_DELROUTE not issued for ppp peer address. Bug or feature?
Date: Mon, 16 Apr 2012 22:21:46 +0200 [thread overview]
Message-ID: <2f6d1271c8c6811acbbc5b2603c72115.squirrel@nlc.no> (raw)
In-Reply-To: <9c375f4b88835bcde92bf3ba8f3434cc@visp.net.lb>
> It looks like "correct" behavior should not harm existing programs that
> much (just there will be netlink message to delete route that are
> already deleted by program, e.g. quagga), but looking to code,
> implementing this feature will make significant overhead and in some
> cases it can be harmful.
> For example if full view BGP interface dropped, it is hundreds of
> thousands netlink messages. So seems better i will listen to
> address/link changes also and keep routing table in memory.
> So better seems to keep as is.
If I understand correct, the "missing" RTM_DELROUTE messages actually
comes from something similar to "ip route flush dev eth0".
If the amount of traffic is a worry, couldn't there be a RTM_FLUSHROUTE or
a special RTM_DELROUTE message that tells that all routes for a given
device is removed?
Stian Skjelstad
next prev parent reply other threads:[~2012-04-16 20:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 12:10 Netlink, route monitoring, RTM_DELROUTE not issued for ppp peer address. Bug or feature? Denys Fedoryshchenko
2012-04-13 13:59 ` SV: " Stian Skjelstad
2012-04-16 10:37 ` Denys Fedoryshchenko
2012-04-16 15:19 ` Stephen Hemminger
2012-04-16 16:48 ` Denys Fedoryshchenko
2012-04-16 20:21 ` Stian Skjelstad [this message]
2012-04-16 21:00 ` Stephen Hemminger
2012-04-17 8:24 ` David Lamparter
2012-04-16 18:40 ` SV: " David Miller
2012-04-16 19:11 ` Denys Fedoryshchenko
2012-04-16 19:29 ` Stephen Hemminger
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=2f6d1271c8c6811acbbc5b2603c72115.squirrel@nlc.no \
--to=stian@nixia.no \
--cc=denys@visp.net.lb \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=stephen.hemminger@vyatta.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).