From: Emmanuel Florac <eflorac@intellique.com>
To: bpm@sgi.com
Cc: xfs@oss.sgi.com
Subject: Re: nfs performance delta between filesystems
Date: Fri, 22 Jan 2010 21:46:24 +0100 [thread overview]
Message-ID: <20100122214624.7095a9c4@galadriel.home> (raw)
In-Reply-To: <20100122183848.GB28561@sgi.com>
Le Fri, 22 Jan 2010 12:38:48 -0600 vous écriviez:
> There were small gains to be had by reordering the sync of the parent
> and child syncs where the two inodes were in the same cluster. The
> larger problem seemed to be that we're not treating the log as stable
> storage. By calling write_inode_now we've written the changes to the
> log first and then gone and also written them out to the inode.
I thought that using nobarrier would prevent the log operations to be
sync'd to disk too quickly? Could I possibly enhance this behaviour by
using an external log on a very fast storage (ramdisk...)?
> nfsd_create, nfsd_link, and nfsd_setattr all do this (or do in the old
> kernel I'm looking at). I have a patchset that changes
> this to an fsync so we force the log and call it good. I'll be happy
> to dust it off if someone hasn't already addressed this situation.
Well, if you think this patchset can be applied to a current kernel
without too much hacking I'm ready to give it a try :)
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-01-22 20:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 17:54 nfs performance delta between filesystems Emmanuel Florac
2010-01-22 18:38 ` bpm
2010-01-22 20:46 ` Emmanuel Florac [this message]
2010-01-23 12:30 ` Dave Chinner
2010-01-25 15:04 ` Christoph Hellwig
2010-01-25 20:28 ` bpm
2010-01-25 20:40 ` Christoph Hellwig
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=20100122214624.7095a9c4@galadriel.home \
--to=eflorac@intellique.com \
--cc=bpm@sgi.com \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox