mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Patrick <steven@ngls.net>
To: Jeff Layton <jlayton@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	bugme-daemon@bugzilla.kernel.org, linux-nfs@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 12564] New: poor performance while preprocessing source code
Date: Wed, 28 Jan 2009 17:02:36 -0800	[thread overview]
Message-ID: <1233190956.21519.13.camel@bluishred.int.infinisim.com> (raw)
In-Reply-To: <20090128170506.37161fb6@tleilax.poochiereds.net>

On Wed, 2009-01-28 at 17:05 -0500, Jeff Layton wrote:
> 
> It's a pretty small patch. The obvious question is: "What mount
> options
> are you using on your NFS mounts?"
> 

  Well, I didn't think that I was using any NFS mounts.
But, it turns out I was in a way.  Apparently, amd does its top
level mounts with noac.  So, where this (using an automounted path):
    cd /h/spo/work
    make -j 5
would be slow.  This (using a non-automounted path):
    cd /home/spo/work
    make -j 5
showed the faster performance I was expecting.
  I will mark my bug as invalid and decide what, if anything,
I want to do about amd.
  Thanks for pointing me in the right direction.

Steven



  reply	other threads:[~2009-01-29  1:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-12564-10286@http.bugzilla.kernel.org/>
2009-01-28 21:29 ` Andrew Morton
2009-01-28 22:05   ` Jeff Layton
2009-01-29  1:02     ` Steven Patrick [this message]
2009-01-29  1:37       ` Andrew Morton
2009-01-29 13:27         ` Trond Myklebust
2009-01-28 22:43   ` Steven Patrick
2009-01-28 23:04     ` Andrew Morton

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=1233190956.21519.13.camel@bluishred.int.infinisim.com \
    --to=steven@ngls.net \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=jlayton@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@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®