From: jlm_devel <jlm_devel@laposte.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: How to notify app of changed cpu/mem/io node configuration?
Date: Wed, 30 Jun 2004 17:37:15 +0000 [thread overview]
Message-ID: <40E2FA4B.7070508@laposte.net> (raw)
In-Reply-To: <20040628173808.04718b83.pj@sgi.com>
Paul Jackson wrote:
>jlm_devel wrote:
>
>
>>using POSIX extended signal to pass some value
>>
>>
>
>sigqueue(2) - thanks for pointing that out - I hadn't realized
>it existed.
>
>
>
thnats why I say that D-BUS reinvent the wheel..... because we can
already use signals to send small pieces of data...... more the linux
kernel now support posix messages queues to send more data and if you
really want to send huge piece of data you can use signal/messages
queues to pass pointers to shared memory objects...... and there this is
blastering fast......
If i'm correct d-bus is used to send some information about hotplug
event such as usb key plug..... signal seems to be more appropriate and
less overhead since they have been optimized for a long time.... we
always reinvent the wheel because we don't know enough the system we're
running on.... QT and other "abstracting" toolkits don't help because
for abstracting you prevent user to use some mechanism that aren't
portable..... ever wondered why the cp command is so blastering fast and
so less cpu consuming ? you need to dig more inside the system
basics..... even the glibc is abstracting and I had the prouf yesterday
with the unlink system call against remove glibc one.....
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-06-30 17:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 0:38 How to notify app of changed cpu/mem/io node configuration? Paul Jackson
2004-06-29 6:24 ` Greg KH
2004-06-29 8:37 ` Paul Jackson
2004-06-29 22:41 ` Dave Hansen
2004-06-29 23:15 ` Paul Jackson
2004-06-29 23:39 ` Dave Hansen
2004-06-29 23:53 ` Rusty Russell
2004-06-30 1:22 ` Paul Jackson
2004-06-30 1:38 ` Dave Hansen
2004-06-30 1:40 ` Paul Jackson
2004-06-30 2:16 ` Paul Jackson
2004-06-30 11:57 ` jlm_devel
2004-06-30 12:26 ` Paul Jackson
2004-06-30 13:08 ` Paul Jackson
2004-06-30 17:37 ` jlm_devel [this message]
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=40E2FA4B.7070508@laposte.net \
--to=jlm_devel@laposte.net \
--cc=linux-hotplug@vger.kernel.org \
/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).