From: Fabio Riccardi <fabio@chromium.com>
To: "J . A . Magallon" <jamagallon@able.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux scheduler limitations?
Date: Thu, 29 Mar 2001 14:51:05 -0800 [thread overview]
Message-ID: <3AC3BC59.9DB44884@chromium.com> (raw)
In-Reply-To: <3AC3A6C9.991472C0@chromium.com> <20010329233521.C6053@werewolf.able.es> <3AC3B35D.FC010700@chromium.com> <20010330003356.C1052@werewolf.able.es>
"J . A . Magallon" wrote:
> It all depends on your app, as every parallel algorithm. In a web-ftp-whatever
> server, you do not need any synchro. You can start threads in free run and
> let them die alone.
even if you don't need synchronization you pay for it anyway, since you will have
to use the pthread version of libc that is reentrant. Moreover many calls (i.e.
accept) are "scheduling points" for pthreads, whenever you call them the runtime
will perform quite a bit of bookeeping.
it is instructive to use a profiler on your application and see what happens when
you use pthreads...
> You said, 'mapped'.
> AFAIK, that is the advantage, you can avoid the VM switch by sharing memory.
If your application uses lots of memory than I agree, Apache only uses a tiny
amount of RAM per instance though, so I don't think that that is my case.
- Fabio
next prev parent reply other threads:[~2001-03-29 22:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-29 21:19 linux scheduler limitations? Fabio Riccardi
2001-03-29 21:26 ` David Lang
2001-03-29 21:55 ` Fabio Riccardi
2001-03-30 1:45 ` Mike Kravetz
2001-03-30 2:58 ` Fabio Riccardi
2001-03-29 21:35 ` J . A . Magallon
2001-03-29 22:12 ` Fabio Riccardi
2001-03-29 22:33 ` J . A . Magallon
2001-03-29 22:51 ` Fabio Riccardi [this message]
2001-03-30 6:52 ` Giuliano Pochini
2001-04-02 22:58 ` Alan Cox
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=3AC3BC59.9DB44884@chromium.com \
--to=fabio@chromium.com \
--cc=jamagallon@able.es \
--cc=linux-kernel@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