From: "David S. Miller" <davem@redhat.com>
To: Richard J Moore <rasman@uk.ibm.com>
Cc: karim@opersys.com, jmorris@redhat.com, zanussi@us.ibm.com,
linux-kernel@vger.kernel.org, bob@watson.ibm.com
Subject: Re: [PATCH][RFC] relayfs (1/4) (Documentation)
Date: Tue, 14 Oct 2003 09:44:24 -0700 [thread overview]
Message-ID: <20031014094424.6cff5697.davem@redhat.com> (raw)
In-Reply-To: <200310141132.28339.rasman@uk.ibm.com>
On Tue, 14 Oct 2003 11:32:28 +0000
Richard J Moore <rasman@uk.ibm.com> wrote:
> Interesting, that assumes sequential processing, if not semi-synchronous
> processing of events on the receiver side, which is far from guaranteed when
> considering low-level tracing especially for flight-recorder applications.
With netlink you may receive the data asynchronously however you
wish after you've requested a dump.
I would like to ask that you go study how netlink works and is used
by things like routing daemons before we discuss this further as
it looks to me like half the conversation is going to be showing
you how netlink works. And hey there's even an RFC on netlink :)
next prev parent reply other threads:[~2003-10-14 16:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 20:59 [PATCH][RFC] relayfs (1/4) (Documentation) Tom Zanussi
2003-10-09 13:45 ` James Morris
2003-10-09 15:25 ` Tom Zanussi
2003-10-09 17:15 ` James Morris
2003-10-09 17:42 ` Karim Yaghmour
2003-10-10 7:57 ` David S. Miller
2003-10-10 14:41 ` Karim Yaghmour
2003-10-11 17:34 ` David S. Miller
2003-10-12 23:23 ` Richard J Moore
2003-10-13 17:25 ` David S. Miller
2003-10-14 11:32 ` Richard J Moore
2003-10-14 16:44 ` David S. Miller [this message]
2003-10-15 16:56 ` Richard J Moore
2003-11-13 14:19 ` Hubertus Franke
2003-10-13 14:53 ` Tom Zanussi
2003-10-10 15:26 ` Tom Zanussi
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=20031014094424.6cff5697.davem@redhat.com \
--to=davem@redhat.com \
--cc=bob@watson.ibm.com \
--cc=jmorris@redhat.com \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rasman@uk.ibm.com \
--cc=zanussi@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.