From: wes chow <wes@woahnelly.net>
To: Dave Nellans <dnellans@cs.utah.edu>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] What is the fastest mechanism for ipc communication under the gentoo-sources kernel
Date: Wed, 23 Jul 2003 10:13:29 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0307231009230.2552@jeeves.woahnelly.net> (raw)
In-Reply-To: <1058931820.23552.4.camel@malfus>
Actually, I'd really start to question the application's realtime
requirements if you start favoring one form of IPC over the other because
of slight performance differences. My advice is to use the mechanism
that's going to require the least amount of maintenance, ie the cleanest
design. Generally, programmer time is more valuable than processor time.
Wes
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-07-23 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 17:07 [gentoo-dev] What is the fastest mechanism for ipc communication under the gentoo-sources kernel Jeff Adams
2003-07-22 18:30 ` Paul de Vrieze
2003-07-23 3:43 ` Dave Nellans
2003-07-23 14:13 ` wes chow [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=Pine.LNX.4.53.0307231009230.2552@jeeves.woahnelly.net \
--to=wes@woahnelly.net \
--cc=dnellans@cs.utah.edu \
--cc=gentoo-dev@gentoo.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