From: Nathan Dabney <smurf@osdlab.org>
To: Hans Reiser <reiser@namesys.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: What is 2.4 Linux networking performance like compared to BSD?
Date: Thu, 1 Mar 2001 11:22:13 -0800 [thread overview]
Message-ID: <20010301112213.B30284@osdlab.org> (raw)
In-Reply-To: <Pine.A41.4.33.0102282123180.68876-100000@aix09.unm.edu> <3A9E72D3.36B28B8F@namesys.com> <20010301090416.E27440@osdlab.org> <3A9E96A6.41D725A3@namesys.com>
In-Reply-To: <3A9E96A6.41D725A3@namesys.com>; from reiser@namesys.com on Thu, Mar 01, 2001 at 09:36:22PM +0300
On Thu, Mar 01, 2001 at 09:36:22PM +0300, Hans Reiser wrote:
> Nathan Dabney wrote:
> >
> > On Thu, Mar 01, 2001 at 07:03:31PM +0300, Hans Reiser wrote:
> >
> > The above link contains some decent squid performance hints for 2.2+Squid.
> >
> > -Nathan Dabney
> It does not say anything about BSD vs. Linux 2.4 networking code.
>
> If I can't get information about BSD v. Linux 2.4 networking code, then reiserfs
> has to get ported to BSD which will be both nice and a pain to do.
>
> Hans
Correct, it only has information which would help tune the setup you first described (the 2.2 setup for your client).
The individuals doing the technical side of that company have a high level of knowledge regarding Linux kernel issues which affect Squid performance and can /possibly/ discuss 2.4 vs. BSD issues with you if you ask.
However, for your client I believe the "technical information" would not be as useful as demonstrated performance. I can't imagine that testing squid would require that much effort when compared to porting resierfs.
It's up to you of course.
-Nathan
next prev parent reply other threads:[~2001-03-01 19:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-28 23:26 What is 2.4 Linux networking performance like compared to BSD? Hans Reiser
2001-03-01 4:25 ` Todd
2001-03-01 16:03 ` Hans Reiser
2001-03-01 17:04 ` Nathan Dabney
2001-03-01 18:36 ` Hans Reiser
2001-03-01 19:16 ` David Weinehall
2001-03-01 19:19 ` Alan Cox
2001-03-02 4:57 ` David L. Parsley
2001-03-01 19:22 ` Nathan Dabney [this message]
2001-03-02 9:02 ` Henning P. Schmiedehausen
2001-03-02 13:00 ` Gregory Maxwell
2001-03-05 8:09 ` Re[2]: " linuxjob
2001-03-02 14:28 ` Alan Cox
2001-03-01 17:17 ` God
2001-03-01 18:04 ` Lincoln Dale
2001-03-01 10:32 ` Alan Cox
2001-03-01 17:15 ` James Lewis Nance
2001-03-01 18:38 ` Hans Reiser
2001-03-01 19:25 ` Tigran Aivazian
2001-03-01 23:30 ` Hans Reiser
2001-03-01 20:26 ` kuznet
2001-03-02 3:05 ` linuxjob
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=20010301112213.B30284@osdlab.org \
--to=smurf@osdlab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.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