From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: tlussnig@bewegungsmelder.de (Thomas Lussnig)
Cc: roy@karlsbakk.net (Roy Sigurd Karlsbakk),
linux-kernel@vger.kernel.org,
khttpd-users@zgp.org (khttpd mailing list)
Subject: Re: [khttpd-users] khttpd vs tux
Date: Sat, 3 Nov 2001 19:21:04 +0000 (GMT) [thread overview]
Message-ID: <E1606Lo-0006ZD-00@the-village.bc.nu> (raw)
In-Reply-To: <3BE44096.2070808@bewegungsmelder.de> from "Thomas Lussnig" at Nov 03, 2001 08:08:06 PM
> on this hardware i think that the problem is the that the Kernel and
> Webserver need to suport that ( each of the 1Gbit card is bound to its
> own process and on Multiprozessor machine that the prozess is fixed to
> one CPU to minimize the siwtch overhead, also im not firm with the
> FibreChannel2
Each GigE card will need its own 66MHz PCI bus. Each PCI bridge will need
to be coming off a memory bus that can sustain all of these and the CPU
at once.
At that point it really doesnt look much like a PC.
next prev parent reply other threads:[~2001-11-03 19:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3BE427CD.702@bewegungsmelder.de>
2001-11-03 18:02 ` [khttpd-users] khttpd vs tux Roy Sigurd Karlsbakk
2001-11-03 19:08 ` Thomas Lussnig
2001-11-03 19:14 ` Roy Sigurd Karlsbakk
2001-11-03 19:21 ` Alan Cox [this message]
2001-11-03 19:18 ` Roy Sigurd Karlsbakk
2001-11-03 19:31 ` J Sloan
2001-11-04 1:19 ` Alan Cox
2001-11-05 10:15 ` Ingo Molnar
2001-11-06 4:46 ` J Sloan
2001-11-03 19:37 ` Alan Cox
2001-11-04 0:07 ` Erik Mouw
2001-11-04 15:32 ` John Alvord
[not found] <3BE42379.2050604@bewegungsmelder.de>
2001-11-03 17:08 ` Roy Sigurd Karlsbakk
[not found] <20011103165129.B26040@fenrus.demon.nl>
2001-11-03 16:56 ` Roy Sigurd Karlsbakk
[not found] <20011103162642.A25824@fenrus.demon.nl>
2001-11-03 16:43 ` Roy Sigurd Karlsbakk
2001-11-03 18:18 ` Miquel van Smoorenburg
2001-11-03 20:24 ` Dirk Moerenhout
2001-11-03 16:21 Roy Sigurd Karlsbakk
2001-11-04 5:26 ` [khttpd-users] " Chul Lee
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=E1606Lo-0006ZD-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=khttpd-users@zgp.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
--cc=tlussnig@bewegungsmelder.de \
/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).