Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
To: linux-mips@linux-mips.org
Subject: Advice needed WRT very slow nfs in new port...
Date: Tue, 28 Jun 2005 14:53:46 -0700	[thread overview]
Message-ID: <42C1C6EA.5080709@avtrex.com> (raw)

I am trying to port 2.6.12 to a 32 bit SOC (ATI Xilleon).  The same 
system is current running 2.4.29 with no problems.

I have an Intel Pro/100M Ethernet adapter on the PCI bus that I use to 
mount the root file system via nfs.  There is also an ohci usb adapter 
on the bus.

My problem is that with my new 2.6.12 port the NFS is very slow.  It 
takes about 10 minutes to mount the root filesystem, run init and 
finally run a shell on the serial port and present the shell prompt. 
Running commands like 'ls' works but can take 15 seconds in a small 
directory.

On the same hardware running 2.4.29 the system boots in 15 seconds and 
there is no delay for the 'ls'.

One theory I have is that there is a problem in either the interrupt or 
timer code somewhere.  My evidence for this is that if I repeatedly plug 
and unplug a usb memory device things run more quickly.  I think the 
interrupts from the USB may be kicking things into action.

Any pointers about where to look would be most appreciated.

Thanks
David Daney

             reply	other threads:[~2005-06-28 21:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-28 21:53 David Daney [this message]
2005-06-30  1:35 ` Problems with Intel e100 driver on new MIPS port, was: Advice needed WRT very slow nfs in new port David Daney
2005-06-30  1:57   ` M. Warner Losh
2005-06-30  2:33     ` David Daney
2005-06-30  2:42       ` M. Warner Losh
2005-06-30  6:25         ` Michael Stickel
2005-06-30 18:23           ` David Daney

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=42C1C6EA.5080709@avtrex.com \
    --to=ddaney@avtrex.com \
    --cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox