All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Rusko <martin.rusko@hp.com>
To: linux-nfs@vger.kernel.org
Cc: "Olle Rämsberg XX" <olle.xx.ramsberg@ericsson.com>
Subject: "ls -l" hangs again since 2.6.34
Date: Mon, 19 Mar 2012 21:58:47 +0100	[thread overview]
Message-ID: <4F679E07.1010100@hp.com> (raw)

Hi,

originally before 2.6.34 kernel there were two lines in nfs_getattr()
function in inode.c file which suspended/resumed process dirtying pages
to allow flush cached changes to NFS server to get mtime/ctime values
set ...

/*
 * Flush out writes to the server in order to update c/mtime.
 *
 * Hold the i_mutex to suspend application writes temporarily;
 * this prevents long-running writing applications from blocking
 * nfs_wb_nocommit.
 */
if (S_ISREG(inode->i_mode)) {
        mutex_lock(&inode->i_mutex);
        nfs_wb_nocommit(inode);
        mutex_unlock(&inode->i_mutex);
}


... however this has been replaced in this commit
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=3fa04ecd72780da31ba8b329e148179bc24a9c7d
and since then again process writing heavily into files on NFS can block
stat calls on these for dozens of seconds.

Is this case, when one process is writing into a file and thus blocking
another process from doing a stat call on it (which means that RPC
GETATTR must be sent and this can't be done before dirty pages are
written to NFS server) handled somewhere in the code, please?

Best Regards,
Martin

PS: Please, Cc me for any reply as I'm not subscribed. Thanks!



                 reply	other threads:[~2012-03-19 20:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4F679E07.1010100@hp.com \
    --to=martin.rusko@hp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=olle.xx.ramsberg@ericsson.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.