| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 6/6] xfs: rename XFS_BUF_ZEROFLAGS macro |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Mon, 8 Feb 2016 01:12:36 -0800 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <1454632683-20543-7-git-send-email-david@xxxxxxxxxxxxx> |
| References: | <1454632683-20543-1-git-send-email-david@xxxxxxxxxxxxx> <1454632683-20543-7-git-send-email-david@xxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.24 (2015-08-30) |
Instead of just renaming it I'd rather dig deeper.
In xlog_bwrite we call xfs_bwrite, which already handles all flag
clearing, so the call to XFS_BUF_ZEROFLAGS can just
be removed.
xlog_sync already sets a lot of these flags again, and is called on an
iclog buffer which never has the READ or XBF_WRITE_FAIL set, so just
replacing it with an opencoded
bp->b_flags &= (XBF_FUA | XBF_FLUSH);
for both instances should be enough, and even that could be moved
into and else clause of the
if (log->l_mp->m_flags & XFS_MOUNT_BARRIER)
conditional.
|
| Previous by Date: | Re: [PATCH 5/6] xfs: remove XBF_STALE flag wrapper macros, Christoph Hellwig |
|---|---|
| Next by Date: | Re: [PATCH 2/3] xfs: don't use ioends for direct write completions, Dave Chinner |
| Previous by Thread: | [PATCH 6/6] xfs: rename XFS_BUF_ZEROFLAGS macro, Dave Chinner |
| Next by Thread: | Re: [PATCH 6/6] xfs: rename XFS_BUF_ZEROFLAGS macro, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |