From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Will Simoneau <simoneau@ele.uri.edu>
Cc: Chuck Lever <chuck.lever@oracle.com>,
Belisko Marek <marek.belisko@gmail.com>,
Trond.Myklebust@netapp.com, bdowning@lavos.net,
linux-nfs@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [bisect] kernel 2.6.38 regression with root nfs mounting
Date: Wed, 30 Mar 2011 06:22:11 +0900 [thread overview]
Message-ID: <20110329212210.GB30482@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110329202408.GM1966@ele.uri.edu>
On Tue, Mar 29, 2011 at 04:24:08PM -0400, Will Simoneau wrote:
> Interestingly, we are both using DM9000 network chips. I wonder if there
> is a UDP-related problem on the DM9000. I will play with my
> configuration a little more (in particular testing proto=tcp and revert
> of 53d4737580535e073963b91ce87d4216e434fab5) but my guess is the DM9000
> driver/chip is to blame. The DM9000A on my board has 16K of on-chip SRAM
> used for its RX/TX buffers which may be playing a part in the problem.
It's more likely that the DM9000 is just slow and fragile. One thing to
note with a lot of the lower end network chips is that you end up
needing to specify rsize and wsize so that you don't get fragmentation -
about 1k tends to work well IME. Otherwise performance often degrades
to the point of unusability.
prev parent reply other threads:[~2011-03-29 21:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimjmdi8sFTTjSPerOVgHQ+pjjwwMvCUX3AJ16At@mail.gmail.com>
2011-03-22 7:52 ` [bisect] kernel 2.6.38 regression with root nfs mounting Belisko Marek
2011-03-22 13:34 ` Steven Rostedt
2011-03-23 6:05 ` Belisko Marek
[not found] ` <43F07477-9075-444D-9BBB-368650538EA8@oracle.com>
2011-03-23 6:30 ` Belisko Marek
2011-03-23 13:44 ` Chuck Lever
2011-03-23 13:44 ` Chuck Lever
2011-03-23 13:46 ` Belisko Marek
2011-03-23 14:06 ` Chuck Lever
[not found] ` <AANLkTik0UgB+k2i=E5t9XcF50SoSr_iXaFYrhctDx0FJ@mail.gmail.com>
2011-03-23 14:54 ` Chuck Lever
2011-03-25 7:24 ` Belisko Marek
2011-03-25 13:26 ` Chuck Lever
2011-03-29 20:24 ` Will Simoneau
2011-03-29 21:22 ` Mark Brown [this message]
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=20110329212210.GB30482@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bdowning@lavos.net \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=marek.belisko@gmail.com \
--cc=simoneau@ele.uri.edu \
/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.