From: Petru Paler <ppetru@ppetru.net>
To: Jakob Østergaard <jakob@unthought.net>,
Andrea Arcangeli <andrea@suse.de>,
Jure Pecar <pegasus@telemach.net>,
linux-kernel@vger.kernel.org, thttpd@bomb.acme.com
Subject: Re: linux 2.2.19pre and thttpd (VM-global problem?)
Date: Fri, 29 Dec 2000 20:21:20 +0200 [thread overview]
Message-ID: <20001229202120.C573@ppetru.net> (raw)
In-Reply-To: <3A4BE9B0.5C809AAC@telemach.net> <20001229032953.A9810@athlon.random> <20001229034712.B9810@athlon.random> <20001229093840.A792@ppetru.net> <20001229165340.C12791@athlon.random> <20001229200421.A8543@ppetru.net> <20001229191328.A12468@unthought.net>
In-Reply-To: <20001229191328.A12468@unthought.net>; from jakob@unthought.net on Fri, Dec 29, 2000 at 07:13:28PM +0100
On Fri, Dec 29, 2000 at 07:13:28PM +0100, Jakob Østergaard wrote:
> > > It can't scale in SMP.
> >
> > No one said it does, but it works nicely on UP.
>
> What ?
Maybe you got me wrong (my english isnt that good): I said that it does
not scale on SMP, but it works just fine on UP.
> The TCP stack is threaded, so things like checksum calculation will
> take advantage of multiple processors - right ?
Wrong. "Threaded" TCP/IP stack -> fine grained locking, not "multiple
threads".
> Thes rest of the work is roughly copying data that isn't already
> cached from the disk into memory. Well, you have one disk so threads
> will buy you zero there.
>
> Unless you do blocking I/O on the files or on the sockets, I fail to
> see how threads could possibly boost the performance on a web server
> that serves *static*only* pages.
They do boost performance on SMP (because you can have N (N=nr. of CPUs)
threads serving data).
> (The reason I'm curious is because I'm about a month away from implementing
> something that would run high-bandwidth TCP transfers and I'm planning
> on keeping it single-threaded - unless someone can tell me that's a bad
> idea)
Keep it single threaded if you run on UP only...
--
Petru Paler, mailto:ppetru@ppetru.net
http://www.ppetru.net - ICQ: 41817235
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-29 18:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-29 1:32 linux 2.2.19pre and thttpd (VM-global problem?) Jure Pecar
2000-12-29 2:29 ` Andrea Arcangeli
2000-12-29 2:47 ` Andrea Arcangeli
2000-12-29 7:38 ` Petru Paler
2000-12-29 15:53 ` Andrea Arcangeli
2000-12-29 18:04 ` Petru Paler
2000-12-29 18:13 ` Jakob Østergaard
2000-12-29 18:21 ` Petru Paler [this message]
2000-12-29 18:56 ` Alan Cox
2000-12-29 19:11 ` Andrea Arcangeli
2000-12-29 18:50 ` Alan Cox
2000-12-29 19:06 ` Andrea Arcangeli
2000-12-29 19:14 ` Andi Kleen
2000-12-29 22:40 ` Jakob Østergaard
2000-12-30 4:21 ` dean gaudet
2000-12-30 17:43 ` Andrea Arcangeli
2000-12-29 8:40 ` Jure Pecar
2000-12-29 11:37 ` Alan Cox
2000-12-29 15:36 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2000-12-29 16:38 Daniel R. Kegel
2000-12-29 21:23 ` Aaron Sethman
2000-12-29 19:29 Matt Liotta
2000-12-29 19:43 ` Andrea Arcangeli
2001-01-01 1:04 Jure Pecar
2001-01-01 21:56 Jure Pecar
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=20001229202120.C573@ppetru.net \
--to=ppetru@ppetru.net \
--cc=andrea@suse.de \
--cc=jakob@unthought.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pegasus@telemach.net \
--cc=thttpd@bomb.acme.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox