It sounds like you are proposing a new family for the netlink
subsystem.
From: "David S. Miller" <davem@redhat.com>
Date:06/16/2003 08:19 PM
Exactly, you have to create this.
Okay. That solves the issue of events generated in a plethora of formats
for the same event. Any suggestions on what should be included in this new
family? I can present a patch to suggest a starting point. However, it
would be great to hear from everyone that has any initial thoughts.
One question that comes to mind, since there is some overlap with netdev
notifier events, should we include those events in the new family? I can
envision a couple of approaches:
1) keep the two interfaces (netdev notifier and netlink), with separate end
users in mind and duplicate the events to each interface. Possibly
thinking about migrating to just one interface over time. Applications
would then just receive one set of events.
2) keep the two interfaces, with no duplication of messages, clarifying the
uses for the two interfaces. An application would then register, and
obtain events from the two separate mechanisms.
p.s. thanks for all the input so far.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/