From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: hadi@cyberus.ca
Cc: "David S. Miller" <davem@davemloft.net>,
akpm@osdl.org, herbert@gondor.apana.org.au, netdev@oss.sgi.com
Subject: Re: 2.6.12-rc4-mm[12] - ULOG problem
Date: Fri, 20 May 2005 18:15:39 +0400 [thread overview]
Message-ID: <1116598539.21310.195.camel@uganda> (raw)
In-Reply-To: <1116589367.6308.36.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
On Fri, 2005-05-20 at 07:42 -0400, jamal wrote:
> On Fri, 2005-20-05 at 10:39 +0400, Evgeniy Polyakov wrote:
>
> > I just want to note, that if you want message bus, you require
> > at least oppsite direction, and thus input callback, and
> > either several socket number for each user [kobject, audit, iscsi,
> > xfrm - all they implement what connector already does] or
> > some header and thus parser in input callback, and thus
> > some registration mechanism.
>
>
> But if you are given your own ID, there should no issues, correct?
Yes.
> i.e it will be no different than say rtnetlink. Users would still have
> to subscribe to topics etc, but thats something you already handle.
> IOW, Iam hoping you are not resorting to a single socket with some user
> space mux to do filtering.
Not following, sorry.
Userspace should use the same socket as kernel - my application
previously
obtained it from dmesg and later used ULOG.
> cheers,
> jamal
>
--
Evgeniy Polyakov
Crash is better than data corruption -- Arthur Grabowski
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-05-20 14:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 3:24 Fw: 2.6.12-rc4-mm[12] - ULOG problem Andrew Morton
2005-05-19 4:49 ` Herbert Xu
2005-05-19 5:27 ` Andrew Morton
2005-05-19 6:31 ` Evgeniy Polyakov
2005-05-19 6:45 ` Andrew Morton
2005-05-19 7:06 ` Evgeniy Polyakov
2005-05-19 7:08 ` Andrew Morton
2005-05-19 7:27 ` Evgeniy Polyakov
2005-05-19 13:19 ` James Morris
2005-05-19 16:53 ` Andrew Morton
2005-05-19 17:09 ` James Morris
2005-05-19 18:54 ` David S. Miller
2005-05-19 18:48 ` David S. Miller
2005-05-20 6:27 ` Evgeniy Polyakov
2005-05-19 18:42 ` David S. Miller
2005-05-20 6:27 ` Evgeniy Polyakov
2005-05-19 18:44 ` David S. Miller
2005-05-20 6:39 ` Evgeniy Polyakov
2005-05-20 11:42 ` jamal
2005-05-20 14:15 ` Evgeniy Polyakov [this message]
2005-05-19 13:16 ` Fw: " James Morris
2005-05-19 13:46 ` jamal
2005-05-19 18:49 ` David S. Miller
2005-05-20 6:25 ` Evgeniy Polyakov
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=1116598539.21310.195.camel@uganda \
--to=johnpol@2ka.mipt.ru \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=herbert@gondor.apana.org.au \
--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).