From: Ben Greear <greearb@candelatech.com>
To: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: PoorMan's San
Date: Mon, 21 Oct 2002 11:10:30 -0700 [thread overview]
Message-ID: <3DB44316.6010204@candelatech.com> (raw)
In-Reply-To: 20021021173141.GA22824@rdlg.net
Robert L. Harris wrote:
>
> Back on the Kernel list after a long hiatis. Need some experienced
> optinions.
>
> Current Setup:
>
> Linux Legato Backup server (E1000 nic) Linux-2.4.19-pre4
> 5xLinux NFS servers (E1000 nic) Linux-2.4.19-pre4
>
> Legato mounts the NFS shares over a Gig ether and uses them as backup
> media for non-offsite/non-longterm. This works very well when NFS
> behaves.
>
> The probems is that every now and then the network/nfs just hang up for
> a while and gets VERY slow. Some research has been done and it seems
> that the PCI latency is part of the problem, especially when IDE Raid
> hits the disks hard, this can overrun the buffers on the GigE card.
>
> I've got a test NFS server coming in and will look at upgrading the
> kernel to 2.4.19-pre11 as there were some bugs associated with E1000 and
> NFS I saw in pre-[7-9] area. I'm also considering trying to use
> Network Block Device instead of NFS. Has anyone tried this?
>
> Any suggestions that doesn't involve hitting up a non-existant budget?
>
>
> Robert
Have you increased the e1000 Rx and Tx descriptors?
Could try the e1000 NAPI patch as well...
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2002-10-21 18:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 17:31 PoorMan's San Robert L. Harris
2002-10-21 18:10 ` Ben Greear [this message]
2002-10-21 18:48 ` D-Link dfe-580tx (nic of doom) Robin Darby
2002-10-22 9:03 ` Gianni Tedesco
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=3DB44316.6010204@candelatech.com \
--to=greearb@candelatech.com \
--cc=Robert.L.Harris@rdlg.net \
--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 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.