* Rtnelink and notifcations: a question.
@ 2013-05-22 6:13 Andy Johnson
0 siblings, 0 replies; only message in thread
From: Andy Johnson @ 2013-05-22 6:13 UTC (permalink / raw)
To: netdev
Hello,
This is a theoretical question (sorry,-)). I was wondering why do we
need both rtnetlink
kernel sockets and the notification API ?
For example,
in net/core/dev.c,
we use notification to send NETDEV_REGISTER event notification in:
call_netdevice_notifiers(NETDEV_REGISTER, dev);
and we use the rtnetlink to send RTM_NEWLINK message:
rtmsg_ifinfo(RTM_NEWLINK,...);
Is it possible to use only the rtnetlink API and to send events like
NETDEV_REGISTER with rtnetlink methods ?
Or is there something inherent with rtnetlink/notification that
prevents implementing in
this way ?
I believe that the other way (solely using notification API) is not
possible because
we need to support getting messages
from userspace (for example, with the iproute package).
Regards,
Andy
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2013-05-22 6:13 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-05-22 6:13 Rtnelink and notifcations: a question Andy Johnson
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).