All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark M. Hoffman" <mhoffman@lightlink.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: make -j4 gets stuck w/ ccache over NFS
Date: Mon, 6 Dec 2004 21:24:29 -0500	[thread overview]
Message-ID: <20041207022429.GA5295@jupiter.solarsys.private> (raw)

Hello:

I'm using ccache version 2.4 [1].  I just changed ~/.ccache to a symbolic
link to a directory which is NFS mounted [2].  The kernel source itself is
on a local FS.  With the ccache suitably primed, when I do a kernel compile
using 'make -j4' it seems to get stuck for seconds at a time.  When it gets
unstuck, it blows through a handful of files and then gets stuck again.

When it is stuck, both NFS client and server are almost totally idle.  The
network itself has almost no other traffic.  It doesn't seem to matter if I
mount NFS w/ udp or tcp (v3 in both cases).

If I move ~/.ccache to a local FS, it never gets stuck.  If I just use 'make'
or even 'make -j2', (I'm pretty sure but not 100%) it never gets stuck.

The NFS client is FC3 with kernel.org 2.6.10-rc3.  I also tried it with -rc1,
2.6.9, and 2.6.8.1 - same problem.

Weirdest part: when I boot the distro stock kernel (2.6.9-1.681_FC3smp) the
problem goes away.  Configs for all of the above are here [3].

Please CC me with replies - thanks!

[1] http://ccache.samba.org/

[2] The NFS server uses kernel 2.4.28-rc2.

[3] http://members.dca.net/mhoffman/lkml-20041213/

-- 
Mark M. Hoffman
mhoffman@lightlink.com


             reply	other threads:[~2004-12-07  2:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-07  2:24 Mark M. Hoffman [this message]
2004-12-07  6:22 ` make -j4 gets stuck w/ ccache over NFS Martin Pool
2004-12-08  7:25 ` tridge
2005-03-10  5:47   ` make -j4 gets stuck w/ ccache over NFS - solved! Mark M. Hoffman
2005-03-10 16:24     ` J. Bruce Fields
2005-03-10 17:11     ` Greg KH

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=20041207022429.GA5295@jupiter.solarsys.private \
    --to=mhoffman@lightlink.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 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.