All of lore.kernel.org
 help / color / mirror / Atom feed
From: tridge@samba.org
To: "Mark M. Hoffman" <mhoffman@lightlink.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: make -j4 gets stuck w/ ccache over NFS
Date: Wed, 8 Dec 2004 18:25:59 +1100	[thread overview]
Message-ID: <16822.44167.836780.288332@samba.org> (raw)
In-Reply-To: <20041207022429.GA5295@jupiter.solarsys.private>

Mark,

 > 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.

I'd suggest you first narrow down the problem to either being a
locking problem or a file IO problem. To do that, change lock_fd() in
util.c in ccache to just "return 0;". That will mean the ccache stats
file could become corrupted, but if it runs fast then you know that it
is a locking problem. I have noticed severe speed problem with NFS
locking on Linux previosly, which is why I mention this as a
possibility.

Note that removing this locking will not cause ccache to produce
incorrect object files, it will just mean the stats printed with
"ccache -s" may be inaccurate.

Cheers, Tridge

PS: I also wonder why you're not just using distcc. It's usually a lot
more appropriate in a distributed environment.


  parent reply	other threads:[~2004-12-08  7:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-07  2:24 make -j4 gets stuck w/ ccache over NFS Mark M. Hoffman
2004-12-07  6:22 ` Martin Pool
2004-12-08  7:25 ` tridge [this message]
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=16822.44167.836780.288332@samba.org \
    --to=tridge@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhoffman@lightlink.com \
    /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.