From: Olaf Kirch <okir@suse.de>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: trond.myklebust@fys.uio.no, nfs@lists.sourceforge.net
Subject: Re: [PATCH] NFS client doesn't flush dirty mmap'd pages during fsync/msync
Date: Tue, 20 Jan 2004 15:58:33 +0100 [thread overview]
Message-ID: <20040120145833.GT17993@suse.de> (raw)
In-Reply-To: <482A3FA0050D21419C269D13989C611302B07B38@lavender-fe.eng.netapp.com>
On Tue, Jan 20, 2004 at 05:55:53AM -0800, Lever, Charles wrote:
> > > With your patch, an fsync degenerates to a global sync
> > > on the mounted file system, if I'm not mistaken.
>
> the patch does not change which list is passed to nfs_scan_list.
> nfs_scan_list is used by nfs_scan_dirty and nfs_scan_commit --
> so it always works on a single file at a time.
Ah, that was the point I missed.
Thanks,
Olaf
--
Olaf Kirch | Stop wasting entropy - start using predictable
okir@suse.de | tempfile names today!
---------------+
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-01-20 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 13:55 [PATCH] NFS client doesn't flush dirty mmap'd pages during fsync/msync Lever, Charles
2004-01-20 14:37 ` trond.myklebust
2004-01-20 14:58 ` Olaf Kirch [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-14 18:46 Chuck Lever
2004-01-20 12:01 ` Olaf Kirch
2004-01-20 13:31 ` trond.myklebust
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=20040120145833.GT17993@suse.de \
--to=okir@suse.de \
--cc=Charles.Lever@netapp.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.