All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Jean Tourrilhes <jt@hpl.hp.com>
Cc: Michal Semler <cijoml@volny.cz>,
	BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Re: [PATCH 2.6] link trigger for AODV and +
Date: Wed, 11 Aug 2004 00:53:23 +0200	[thread overview]
Message-ID: <1092178402.4564.204.camel@pegasus> (raw)
In-Reply-To: <20040810163203.GA1963@bougret.hpl.hp.com>

Hi Jean,

> > If the HCI connections themself are fully integrated into the driver and
> > device model an event through hotplug would be the best. Comments?
> 
> 	I personally don't like hotplug for this application. Hotplug
> force the event to go through a bunch of scripts, which is good for
> simple config and daemon-less stuff, but bad for daemons.
> 	Let say you have a big daemon monitoring a bunch of stuff and
> keeping track of state. Examples are pand, waproamd, MobileIP... With
> hotplug you have to write a script that somehow forward the event to
> the daemon. As events are usually passed via Unix sockets, shared
> memory or something similar, the scripts need to call a little program
> generating the event.
> 	Therefore you have :
> 		hotplug event ->
> 			-> my shell script
> 				-> my tiny program
> 					-> Unix socket or shared memory
> 						-> My daemon
> 	For each event, you need to create two processes (shell script
> and tiny program) than need to be paged from disk. Yuck...
> 	If you look at waproamd, it uses exclusively the RtNetlink
> events, even though the equivalent events exist in Hotplug.

you are right, but there are pros and cons on both sides and I like to
find the best solution. However I never looked at RtNetlink before. I
think that I should educate myself a little bit more.

> > > > I sent the full patch for inclusion, but it came out that one part
> > > > causes troubles and so I removed this part. I didn't found the time for
> > > > a further investigation.
> > > 
> > > 	That's what I said : I'm going to test it properly. If you
> > > could remember the issue, that would help.
> > 
> > I searched the email exchange between Michal and me from the mailing
> > list archives for you. Check out this thread:
> > 
> > 	http://thread.gmane.org/gmane.linux.bluez.user/2672
> 
> 	The bug is obvious, you forgot that in 2.4.X the list doesn't
> point to struct sock but to struct bluez_pinfo. Compare your patch to
> the version below.

What a stupid mistake. I must been blind at that time :(

Regards

Marcel




-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-08-10 22:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05  1:33 [PATCH 2.6] link trigger for AODV and + Jean Tourrilhes
2004-08-08 14:49 ` [Bluez-devel] " Marcel Holtmann
2004-08-09 18:51   ` Jean Tourrilhes
2004-08-09 19:08     ` [Bluez-devel] " Marcel Holtmann
2004-08-09 19:54       ` Jean Tourrilhes
2004-08-10  8:13         ` [Bluez-devel] " Marcel Holtmann
2004-08-10 16:32           ` Jean Tourrilhes
2004-08-10 22:53             ` Marcel Holtmann [this message]
2004-08-10 23:37               ` Jean Tourrilhes

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=1092178402.4564.204.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=cijoml@volny.cz \
    --cc=jt@hpl.hp.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.