From: Matt Helsley <matthltc@us.ibm.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Libor Vanek <libor.vanek@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Subject: Re: Connector - how to start?
Date: Fri, 14 Apr 2006 20:07:17 -0700 [thread overview]
Message-ID: <1145070437.28705.73.camel@stark> (raw)
In-Reply-To: <20060414192634.697cd2e3.rdunlap@xenotime.net>
On Fri, 2006-04-14 at 19:26 -0700, Randy.Dunlap wrote:
> On Sat, 15 Apr 2006 03:09:05 +0200 Libor Vanek wrote:
>
> > Hi,
> > I'd like to start writing some small module using connector to send
> > messages to/from user-space. Unfortunately I'm absolutely not familiar
> > with netlink/connector API usage and I couldn't find any usefull
> > documentation (yes, I read Documentation/connector/ and tried Google).
> >
> > So here's things which are not clear to me:
> > - the Documentation/connector containts only kernel-space example -
> > don't anybody have also "user-space client example"?
> > - how do I ACK message sent to/from user-space?
> > - in case of multiple clients listening how do I send message just to
> > (random) one (simple load balancing) or to all of them? (broadcasting)
> > - is there some "easy" way how to send longer messages then
> > CONNECTOR_MAX_MSG_SIZE?
>
> There was a connector userspace example posted to lkml on
> 2005-SEP-28:
>
> Subject: [RFC] Process Events Connector (test program)
> From: Matthew Helsley <matthltc@us.ibm.com>
>
>
> It seems like one of the Red Hat guys had some netlink documentation
> and sample programs at people.redhat.com, but I can't find that
> just now.
>
> ---
> ~Randy
Subject:[ANNOUNCE] Test Program for Filesystem Events Reporter
From:
Yi Yang <yang.y.yi@gmail.com>
might demonstrate what you're looking for as well.
I don't believe there is an existing way to send messages longer than
CONNECTOR_MAX_MSG_SIZE. Perhaps you could send multiple messages with
the same sequence number but a different "fragment number" in the
message.
However, if you're sending messages much larger than
CONNECTOR_MAX_MSG_SIZE perhaps the medium of communication is not
appropriate. Have you considered relay files?
Cheers,
-Matt Helsley
next prev parent reply other threads:[~2006-04-15 3:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-15 1:09 Connector - how to start? Libor Vanek
2006-04-15 2:26 ` Randy.Dunlap
2006-04-15 3:07 ` Matt Helsley [this message]
2006-04-15 9:18 ` Evgeniy Polyakov
[not found] ` <369a7ef40604150350x8e7dea1sbf1f83cb800dd1c3@mail.gmail.com>
2006-04-15 11:14 ` Evgeniy Polyakov
2006-04-15 12:18 ` Paul Collins
2006-04-15 12:38 ` Evgeniy Polyakov
[not found] ` <369a7ef40604150624n28da8895if158a2c13cac2b9e@mail.gmail.com>
2006-04-16 7:53 ` Evgeniy Polyakov
2006-04-16 17:09 ` Evgeniy Polyakov
[not found] ` <369a7ef40604160426s301dcd52r4c9826698d3d2f79@mail.gmail.com>
2006-04-16 11:40 ` Evgeniy Polyakov
[not found] ` <369a7ef40604160509xcf2caadi782b90da956639d5@mail.gmail.com>
2006-04-16 13:25 ` Evgeniy Polyakov
[not found] ` <369a7ef40604160632t16f6aab9u687a6b359997d7ea@mail.gmail.com>
2006-04-16 14:19 ` Evgeniy Polyakov
2006-04-18 6:07 ` Evgeniy Polyakov
[not found] ` <369a7ef40604190439v6e8f1bf6lf52cfab5af3a93af@mail.gmail.com>
2006-04-19 12:14 ` Evgeniy Polyakov
2006-04-20 15:12 ` Libor Vanek
2006-04-20 15:25 ` Evgeniy Polyakov
2006-04-20 15:32 ` Libor Vanek
2006-04-15 21:48 ` Jon Masters
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=1145070437.28705.73.camel@stark \
--to=matthltc@us.ibm.com \
--cc=johnpol@2ka.mipt.ru \
--cc=libor.vanek@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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.