From: Adam Nielsen <a.nielsen@shikadi.net>
To: linux-kernel@vger.kernel.org
Subject: Why do programs freeze with big network transfers?
Date: Thu, 30 Dec 2010 17:25:22 +1000 [thread overview]
Message-ID: <ifhc54$efg$1@dough.gmane.org> (raw)
Hi all,
I'm a bit stuck on this problem so I hope someone can help. My desktop PC is
running kernel 2.6.33.1 and when I copy some largish files (2-3GB each) onto
an NFS share my PC becomes unusable, pretty much locking up for 60 seconds at
a time.
Everything works fine for a little while once the copy has begun - the files
are read off the software-RAID-0 disks at about 200MB/sec, then after 10
seconds or so data starts going across the gigabit network at about 40MB/sec
(speed limited by the target system which pegs at 100% CPU due to lack of
jumbo packets.)
After a few seconds of data going over the network, X-Windows freezes. No
screen updates, the mouse cursor won't move, for all intents and purposes the
system has frozen solid. I'm playing music with XMMS2 and that keeps going,
but occasionally even that stops too. After a minute (between 45 and 65
seconds) everything unfreezes and keeps going as per normal. Less than 10
seconds later everything freezes again for another minute! This keeps going
until the file transfer has finished.
When things unfreeze the disk is idle, and within 10 seconds the disk starts
up again and almost immediately the next minute-long freeze begins. While
things are frozen the network transfer continues, and bizarrely I can log in
to the machine over SSH where everything seems normal. 'top' reports most
processes are idle, and running a command line XMMS2 client happily reports
that the song I am listening to is stuck at exactly the same point until the
freeze is over, when the seconds start counting up again.
The reason I am stuck is that nothing is appearing in dmesg, so it appears the
kernel is unaware of the problem. Has anyone seen anything like this before?
I'm not sure what to do next.
Disks are connected to an Intel ICH9 SATA controller in AHCI mode, LAN is a
Realtek 8169, video card is nVidia GeForce 8600. Perhaps some combination of
this is to blame?
I have tried using cat to read these files into /dev/null and the system will
happily read the files at full speed without freezing, and I have used ttcp's
speed test function to send data over the network at full speed, which also
works without X11 freezing. Doing this at the same time (reading from the
disk and sending network traffic) also works fine without locking up, so it
seems the problems only arise when NFS gets involved.
'mount' reports the options on the NFS share as:
rw,user=adam,tcp,soft,intr,timeo=20,vers=3,addr=192.168.0.6
Any suggestions about what I can do next?
Many thanks,
Adam.
next reply other threads:[~2010-12-30 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 7:25 Adam Nielsen [this message]
2010-12-30 7:58 ` Why do programs freeze with big network transfers? Eric Dumazet
2010-12-31 1:20 ` Adam Nielsen
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='ifhc54$efg$1@dough.gmane.org' \
--to=a.nielsen@shikadi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox