From: Stefan Rompf <srompf@isg.de>
To: jamal <hadi@cyberus.ca>
Cc: Michael Richardson <mcr@sandelman.ottawa.on.ca>, netdev@oss.sgi.com
Subject: Re: Patch: Device operative state notification against 2.5.7
Date: Tue, 09 Apr 2002 13:28:37 +0200 [thread overview]
Message-ID: <3CB2D065.A3DA60BB@isg.de> (raw)
In-Reply-To: Pine.GSO.4.30.0204072343250.12041-100000@shell.cyberus.ca
Hi Jamal,
> [discussion whether IFOP_DOWN_LOWERLAYER should send netlink messages]
>
> I think they should be accessible; whether you send netlink
> advertisements everytime there is some state transition is the question.
they should. For a routing daemon it is interesting to be notified when
interfaces becomes capable or incapable of handling packets, independant
of the reason. As long as we abstract virtual or subinterfaces as normal
interfaces to the upper layers (which is IMHO the correct decision),
IFOP_DOWN_LOWERLAYER must trigger a notification.
Stefan
next prev parent reply other threads:[~2002-04-09 11:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3CACB9BC.4D585C25@isg.de>
2002-04-07 20:16 ` Patch: Device operative state notification against 2.5.7 jamal
2002-04-07 20:26 ` jamal
2002-04-08 17:48 ` David Brownell
2002-04-07 22:11 ` Michael Richardson
2002-04-08 11:59 ` jamal
2002-04-09 11:28 ` Stefan Rompf [this message]
2002-04-11 11:24 ` jamal
2002-04-12 10:12 ` Stefan Rompf
2002-04-09 11:43 ` QoS _put, _get and _delete class ops semantic Martin Devera
2002-04-11 12:35 ` jamal
2002-04-11 13:41 ` Martin Devera
2002-04-11 14:42 ` jamal
[not found] <Pine.GSO.4.30.0203302133110.7012-100000@shell.cyberus.ca>
2002-03-31 10:23 ` Patch: Device operative state notification against 2.5.7 Stefan Rompf
2002-03-31 16:21 ` jamal
2002-04-01 14:44 ` Stefan Rompf
2002-04-01 16:25 ` jamal
2002-04-01 20:31 ` David Brownell
2002-04-02 3:05 ` jamal
2002-03-31 10:23 ` Stefan Rompf
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=3CB2D065.A3DA60BB@isg.de \
--to=srompf@isg.de \
--cc=hadi@cyberus.ca \
--cc=mcr@sandelman.ottawa.on.ca \
--cc=netdev@oss.sgi.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).