From: jamal <hadi@cyberus.ca>
To: Thomas Graf <tgraf@suug.ch>
Cc: Andrew Morton <akpm@osdl.org>,
Guillaume Thouvenin <guillaume.thouvenin@bull.net>,
kaigai@ak.jp.nec.com, marcelo.tosatti@cyclades.com,
"David S. Miller" <davem@redhat.com>,
jlan@sgi.com, lse-tech@lists.sourceforge.net,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
elsa-devel@lists.sourceforge.net
Subject: Re: [Lse-tech] Re: A common layer for Accounting packages
Date: 28 Feb 2005 08:40:10 -0500 [thread overview]
Message-ID: <1109598010.2188.994.camel@jzny.localdomain> (raw)
In-Reply-To: <20050228132051.GO31837@postel.suug.ch>
netlink broadcast or a wrapper around it.
Why even bother doing the check with netlink_has_listeners()?
cheers,
jamal
On Mon, 2005-02-28 at 08:20, Thomas Graf wrote:
> > Havent seen the beginnings of this thread. But whatever you are trying
> > to do seems to suggest some complexity that you are trying to
> > workaround. What was wrong with just going ahead and just always
> > invoking your netlink_send()?
>
> I guess parts of the wheel are broken and need to be reinvented ;->
>
> > If there are nobody in user space (or kernel) listening, it wont go anywhere.
>
> Additional you may want to extend netlink a bit to check whether
> there is a listener before creating the messages. The method to do so
> depends on whether you use netlink_send() or netlink_brodacast(). The
> latter is more flexiable because you can add more groups later on
> and the userspace applications can decicde which ones they want to
> listen to. Both methods handle dying clients perfectly fine, the
> association to the netlink socket gets destroyed as soon as the socket
> is closed. Therefore you can simply check mc_list of the netlink
> protocol you use to see if there are any listeners registered:
>
> static inline int netlink_has_listeners(struct sock *sk)
> {
> int ret;
>
> read_lock(&nl_table_lock);
> ret = list_empty(&nl_table[sk->sk_protocol].mc_list)
> read_unlock(&nl_table_lock);
>
> return !ret;
> }
>
> This is simplified and ignores the actual group assignments, i.e. you
> might want to extend it to have it check if there are listeners for
> a certain group.
>
next prev parent reply other threads:[~2005-02-28 13:41 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-19 0:51 A common layer for Accounting packages Jay Lan
2005-02-19 1:16 ` Andrew Morton
2005-02-21 6:51 ` Guillaume Thouvenin
2005-02-22 20:11 ` [Lse-tech] " Jay Lan
2005-02-23 7:30 ` Guillaume Thouvenin
2005-02-21 7:54 ` Kaigai Kohei
2005-02-22 20:26 ` Jay Lan
2005-02-23 7:07 ` Kaigai Kohei
2005-02-23 7:20 ` Andrew Morton
2005-02-23 8:33 ` Guillaume Thouvenin
2005-02-23 8:51 ` Andrew Morton
2005-02-23 9:30 ` Guillaume Thouvenin
2005-02-23 9:36 ` Andrew Morton
2005-02-23 19:11 ` Jay Lan
2005-02-24 7:42 ` Guillaume Thouvenin
2005-02-23 9:50 ` Tim Schmielau
2005-02-24 22:27 ` Jay Lan
2005-02-23 11:29 ` Kaigai Kohei
2005-02-23 20:48 ` Jay Lan
2005-02-25 5:07 ` Kaigai Kohei
2005-02-25 5:28 ` Andrew Morton
2005-02-25 17:32 ` Jay Lan
2005-02-25 17:45 ` Chris Wright
2005-02-25 18:11 ` Jay Lan
2005-02-25 21:30 ` Andrew Morton
2005-02-25 22:18 ` Jay Lan
2005-02-27 9:49 ` Marcelo Tosatti
2005-02-27 15:20 ` KaiGai Kohei
2005-02-27 14:03 ` Marcelo Tosatti
2005-02-27 19:27 ` David S. Miller
2005-02-28 1:59 ` Kaigai Kohei
2005-02-28 2:32 ` Thomas Graf
2005-02-28 5:17 ` Evgeniy Polyakov
2005-02-28 7:20 ` Guillaume Thouvenin
2005-02-28 7:39 ` Andrew Morton
2005-02-28 8:04 ` Evgeniy Polyakov
2005-02-28 12:10 ` jamal
2005-02-28 9:29 ` Marcelo Tosatti
2005-02-28 13:20 ` Thomas Graf
2005-02-28 13:40 ` jamal [this message]
2005-02-28 13:53 ` Thomas Graf
2005-02-28 9:52 ` Marcelo Tosatti
2005-02-28 14:10 ` jamal
2005-02-28 14:25 ` Thomas Graf
2005-02-28 15:31 ` jamal
2005-02-28 16:17 ` Evgeniy Polyakov
2005-03-01 8:21 ` Guillaume Thouvenin
2005-03-01 13:38 ` Kaigai Kohei
2005-03-01 13:53 ` Guillaume Thouvenin
2005-03-01 14:17 ` Evgeniy Polyakov
2005-03-02 4:50 ` Paul Jackson
2005-03-02 8:58 ` Guillaume Thouvenin
2005-03-02 9:06 ` Andrew Morton
2005-03-02 9:25 ` Guillaume Thouvenin
2005-03-02 15:30 ` Paul Jackson
2005-03-01 20:40 ` Paul Jackson
2005-02-24 1:25 ` Paul Jackson
2005-02-24 1:56 ` Jay Lan
2005-02-24 2:07 ` Paul Jackson
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=1109598010.2188.994.camel@jzny.localdomain \
--to=hadi@cyberus.ca \
--cc=akpm@osdl.org \
--cc=davem@redhat.com \
--cc=elsa-devel@lists.sourceforge.net \
--cc=guillaume.thouvenin@bull.net \
--cc=jlan@sgi.com \
--cc=kaigai@ak.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=marcelo.tosatti@cyclades.com \
--cc=netdev@oss.sgi.com \
--cc=tgraf@suug.ch \
/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).