From: Eric Dumazet <eric.dumazet@gmail.com>
To: Manavalan Krishnan <manavalan_k@yahoo.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: Large file copy to NFS mounted directory causes delay in other application packets
Date: Wed, 09 Nov 2011 09:59:09 +0100 [thread overview]
Message-ID: <1320829149.2315.6.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> (raw)
In-Reply-To: <1320826389.47194.YahooMailNeo@web160716.mail.bf1.yahoo.com>
Please dont top post on these lists, thanks.
Le mercredi 09 novembre 2011 à 00:13 -0800, Manavalan Krishnan a écrit :
> (1) NFS is using TCP
> (2) yes eth0 is dedicated to heartbeat and eth1 is dedicated to NFS
> (3) I notice the following at the system where file copy is occuring
>
> The kernel Recv-Q of the heartbeat application socket grows but not delivered to the socket recv call.
> Here is the netstat output.
>
> Proto Recv-Q Send-Q Local Address Foreign Address
>
> udp 11522 0 *:23435 *:*
>
OK so the sending side is OK : The delay is at receiver side.
Note that since netstat shows receive queue has some skbs, it should be
available to heartbeat daemon immediately.
> As soon as I stop the file transfer, the socket recv call receives the packets and Recv-Q goes 0.
> (4) The server has 4 cpu cores and 25G RAM
>
1) How many nfsd threads are running ?
grep th /proc/net/rpc/nfsd
2) WHat kind of NIC do you use ?
lsmod , lspci
3) Hmm, are IRQ to eth0/eth1 handled by same cpu ?
grep eth /proc/interrupts
4) You could try to cpu affine all nfsd to cpu0,cpu1,cpu2 and heartbeat
daemon to cpu3.
man taskset
5) You could 'strace -ttt' heartbeat daemon to check if it is not
blocked on some local disk access (it competes with all nfsd threads)
next prev parent reply other threads:[~2011-11-09 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1320816503.73813.YahooMailNeo@web160718.mail.bf1.yahoo.com>
2011-11-09 6:24 ` Large file copy to NFS mounted directory causes delay in other application packets Eric Dumazet
2011-11-09 8:13 ` Manavalan Krishnan
2011-11-09 8:59 ` Eric Dumazet [this message]
[not found] ` <CAA93jw4gDuHyG508zxRzyn+MJ4gL5m958OaCWJxoDsaLgjdnqg@mail.gmail.com>
2011-11-09 8:42 ` Manavalan Krishnan
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=1320829149.2315.6.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC \
--to=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manavalan_k@yahoo.com \
--cc=netdev@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