mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Russell Miller" <duskglow@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: nfs NULL procedure packets
Date: Wed, 3 Dec 2008 10:11:26 -0800	[thread overview]
Message-ID: <4eea36270812031011x5f014b04q352af666cacb2f93@mail.gmail.com> (raw)

Hi again, I was hoping someone here could answer another question.  I
apologize if these are easy questions...

So a couple of days ago I was troubleshooting yet another NFS problem
(not the non-one I described a few days ago).  I sent a 1G file over
to a server, did a TCP capture, and analyzed the results.

I noticed a lot of NULL procedure packets.  A *lot* of them.  In some
cases, one every 10 microseconds, and there were about 400,000 of them
I captured.

This seems like a lot of network traffic for very little reason.

Is this normal behavior, or something I should investigate further?
It seems to me like pinging the NFS server once every 10 microseconds
is a major waste of bandwidth.

--Russell

             reply	other threads:[~2008-12-03 18:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03 18:11 Russell Miller [this message]
2008-12-04 18:45 ` J. Bruce Fields

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=4eea36270812031011x5f014b04q352af666cacb2f93@mail.gmail.com \
    --to=duskglow@gmail.com \
    --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
all inboxes | Powered by JetHome®