| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 2/7] xfs: Use delayed write for inodes rather than async |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Mon, 25 Jan 2010 10:29:31 -0500 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <1264400564-19704-3-git-send-email-david@xxxxxxxxxxxxx> |
| References: | <1264400564-19704-1-git-send-email-david@xxxxxxxxxxxxx> <1264400564-19704-3-git-send-email-david@xxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.19 (2009-01-05) |
> /*
> - * Write out the inode. The completion routine ('iflush_done') will
> - * pull it from the AIL, mark it clean, unlock the flush lock.
> + * Push the inode to it's backing buffer. This will not remove
> + * the inode from the AIL - a further push will be required to trigger
> + * a buffer push. However, this allows all the dirty inodes to be
> pushed to
Btw, this creates a rather annoying and pointless too long line in the
source file.
|
| Previous by Date: | Re: nfs performance delta between filesystems, Christoph Hellwig |
|---|---|
| Next by Date: | Re: Assistance needed mounting XFS version 1 filesystem, Jordan |
| Previous by Thread: | Re: [PATCH 2/7] xfs: Use delayed write for inodes rather than async, Christoph Hellwig |
| Next by Thread: | [PATCH 7/7] xfs: xfs_fs_write_inode() can fail to write inodes synchronously, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |