From: Stephen Lord <lord@sgi.com>
To: Samuel Flory <sflory@rackable.com>
Cc: Andrea Arcangeli <andrea@suse.de>,
Austin Gonyou <austin@coremetrics.com>,
Christian Guggenberger
<christian.guggenberger@physik.uni-regensburg.de>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-xfs@oss.sgi.com
Subject: Re: 2.4.20pre5aa2
Date: 13 Sep 2002 14:17:42 -0500 [thread overview]
Message-ID: <1031944671.1534.34.camel@snafu> (raw)
In-Reply-To: <3D813CFB.7050200@rackable.com>
On Thu, 2002-09-12 at 20:18, Samuel Flory wrote:
>
> The system has 4G of ram, and 4G of swap. So real memory is not an
> issue. The system is a intended to be an nfs server. As a result nfs
> performance is my only real concern. I should really use CONFIG_3GB as
> I'm not doing much in user space other a tftp, and dhcp server.
>
> In any case the system isn't in production so I can leave it as is
> till monday.
>
So, after backing out 00_net-softirq (this was killing my networking
and NFS setup for some reason) and applying the new scheduler
related fix in xfs, I have had this kernel up a few hours running
dbench and a bunch of other things, it has not hung once or exhibited
any other problems.
Having said that, my environment is different, I do not have 4G of
memory, I have 128M, and I also do not have md - not enough disks
right now to do that.
Steve
--
Steve Lord voice: +1-651-683-3511
Principal Engineer, Filesystem Software email: lord@sgi.com
next prev parent reply other threads:[~2002-09-13 19:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 18:16 2.4.20pre5aa2 Christian Guggenberger
2002-09-11 18:24 ` 2.4.20pre5aa2 Austin Gonyou
2002-09-11 18:28 ` 2.4.20pre5aa2 Christian Guggenberger
[not found] ` <1031769317.24629.28.camel@UberGeek.coremetrics.com>
2002-09-11 18:45 ` 2.4.20pre5aa2 Christian Guggenberger
2002-09-11 18:51 ` 2.4.20pre5aa2 Austin Gonyou
2002-09-11 18:41 ` 2.4.20pre5aa2 Andrea Arcangeli
2002-09-12 23:29 ` 2.4.20pre5aa2 Samuel Flory
2002-09-12 23:45 ` 2.4.20pre5aa2 Stephen Lord
2002-09-13 0:06 ` 2.4.20pre5aa2 Samuel Flory
2002-09-13 0:23 ` 2.4.20pre5aa2 Andrea Arcangeli
2002-09-13 0:47 ` 2.4.20pre5aa2 Stephen Lord
2002-09-13 0:54 ` 2.4.20pre5aa2 Andrea Arcangeli
2002-09-13 2:14 ` 2.4.20pre5aa2 Samuel Flory
2002-09-13 12:53 ` 2.4.20pre5aa2 Andrea Arcangeli
2002-09-13 21:09 ` 2.4.20pre5aa2 Samuel Flory
2002-09-13 21:18 ` 2.4.20pre5aa2 Andrea Arcangeli
2002-09-14 14:39 ` 2.4.20pre5aa2 Stephen Lord
2002-09-15 11:13 ` 2.4.20pre5aa2 Andi Kleen
2002-09-15 19:39 ` 2.4.20pre5aa2 Samuel Flory
2002-09-16 16:03 ` 2.4.20pre5aa2 Dave Hansen
2002-09-16 16:20 ` 2.4.20pre5aa2 Andrea Arcangeli
2002-09-16 16:39 ` 2.4.20pre5aa2 Dave Hansen
2002-09-13 1:27 ` 2.4.20pre5aa2 Samuel Flory
2002-09-13 2:14 ` 2.4.20pre5aa2 Samuel Flory
2002-09-13 1:18 ` 2.4.20pre5aa2 Samuel Flory
2002-09-13 19:17 ` Stephen Lord [this message]
2002-09-11 18:44 ` 2.4.20pre5aa2 Christoph Hellwig
2002-09-11 19:11 ` 2.4.20pre5aa2 Christian Guggenberger
-- strict thread matches above, loose matches on Subject: below --
2002-09-09 16:50 2.4.20pre5aa2 Andrea Arcangeli
2002-09-10 18:51 ` 2.4.20pre5aa2 Joe Kellner
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=1031944671.1534.34.camel@snafu \
--to=lord@sgi.com \
--cc=andrea@suse.de \
--cc=austin@coremetrics.com \
--cc=christian.guggenberger@physik.uni-regensburg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=sflory@rackable.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.