From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Carlos Maiolino <cmaiolino@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 0/4] Buffer's log item refactoring
Date: Fri, 19 Jan 2018 13:43:41 -0800 [thread overview]
Message-ID: <20180119214341.GK25805@magnolia> (raw)
In-Reply-To: <20180119140847.22934-1-cmaiolino@redhat.com>
On Fri, Jan 19, 2018 at 03:08:43PM +0100, Carlos Maiolino wrote:
> Hi,
>
> A few time ago Christoph suggested to use list_head API to handle buffer's
> log_item_list.
>
> This patchset aims to split the current bp->b_fspriv field into a specific field
> to hold the xfs_buf_log_item, and another to hold the list of log items attached
> to the buffer (3rd patch), and finally replace the singly linked list
> implementation by the list_head infra-structure (4th patch).
>
> The first two patches are just a typedef removal of xfs_buf_log_item_t and
> xfs_buf_t, I did while studying how all the buffer I/O mechanism works, I
> thought since we plan to get rid of the typedefs in future, this might be
> useful.
>
> I can rebase the 3rd and 4th patch on top of current xfs tree if the typedef
> removal patches are useless, you guys call.
Typedef removal seems useful... is this series based atop current for-next?
--D
> This patchset survived several xfstests runs.
>
> Cheers.
>
> Carlos Maiolino (4):
> Get rid of xfs_buf_log_item_t typedef
> Get rid of xfs_buf_t typedef
> Split buffer's b_fspriv field
> Use list_head infra-structure for buffer's log items list
>
> fs/xfs/libxfs/xfs_alloc.c | 36 ++++----
> fs/xfs/libxfs/xfs_attr_leaf.c | 2 +-
> fs/xfs/libxfs/xfs_bmap.c | 8 +-
> fs/xfs/libxfs/xfs_btree.c | 26 +++---
> fs/xfs/libxfs/xfs_btree.h | 2 +-
> fs/xfs/libxfs/xfs_da_btree.c | 2 +-
> fs/xfs/libxfs/xfs_dir2_block.c | 2 +-
> fs/xfs/libxfs/xfs_dir2_data.c | 2 +-
> fs/xfs/libxfs/xfs_dir2_leaf.c | 2 +-
> fs/xfs/libxfs/xfs_dir2_node.c | 2 +-
> fs/xfs/libxfs/xfs_ialloc.c | 18 ++--
> fs/xfs/libxfs/xfs_inode_buf.c | 4 +-
> fs/xfs/libxfs/xfs_rtbitmap.c | 22 ++---
> fs/xfs/libxfs/xfs_sb.c | 2 +-
> fs/xfs/libxfs/xfs_symlink_remote.c | 2 +-
> fs/xfs/xfs_buf.c | 140 +++++++++++++++----------------
> fs/xfs/xfs_buf.h | 21 ++---
> fs/xfs/xfs_buf_item.c | 166 ++++++++++++++++++++-----------------
> fs/xfs/xfs_buf_item.h | 7 +-
> fs/xfs/xfs_dquot.c | 22 ++---
> fs/xfs/xfs_dquot_item.c | 2 +-
> fs/xfs/xfs_fsops.c | 2 +-
> fs/xfs/xfs_inode.c | 24 +++---
> fs/xfs/xfs_inode_item.c | 41 +++------
> fs/xfs/xfs_itable.c | 2 +-
> fs/xfs/xfs_log.c | 26 +++---
> fs/xfs/xfs_log_recover.c | 46 +++++-----
> fs/xfs/xfs_qm.c | 8 +-
> fs/xfs/xfs_rtalloc.c | 20 ++---
> fs/xfs/xfs_rtalloc.h | 4 +-
> fs/xfs/xfs_symlink.c | 22 ++---
> fs/xfs/xfs_trans.c | 2 +-
> fs/xfs/xfs_trans.h | 4 +-
> fs/xfs/xfs_trans_buf.c | 104 ++++++++++++-----------
> 34 files changed, 397 insertions(+), 398 deletions(-)
>
> --
> 2.14.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-01-19 21:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 14:08 [PATCH 0/4] Buffer's log item refactoring Carlos Maiolino
2018-01-19 14:08 ` [PATCH 1/4] Get rid of xfs_buf_log_item_t typedef Carlos Maiolino
2018-01-20 3:33 ` Darrick J. Wong
2018-01-19 14:08 ` [PATCH 2/4] Get rid of xfs_buf_t typedef Carlos Maiolino
2018-01-20 3:35 ` Darrick J. Wong
2018-01-19 14:08 ` [PATCH 3/4] Split buffer's b_fspriv field Carlos Maiolino
2018-01-19 14:08 ` [PATCH 4/4] Use list_head infra-structure for buffer's log items list Carlos Maiolino
2018-01-19 18:21 ` Darrick J. Wong
2018-01-19 18:50 ` Carlos Maiolino
2018-01-23 10:19 ` Nikolay Borisov
2018-01-23 13:05 ` Carlos Maiolino
2018-01-23 14:55 ` Nikolay Borisov
2018-01-23 18:10 ` Darrick J. Wong
2018-01-24 8:44 ` Carlos Maiolino
2018-01-19 21:43 ` Darrick J. Wong [this message]
2018-01-20 4:54 ` [PATCH 0/4] Buffer's log item refactoring Dave Chinner
2018-01-22 11:39 ` Carlos Maiolino
2018-01-22 21:42 ` Darrick J. Wong
2018-01-23 8:39 ` Carlos Maiolino
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=20180119214341.GK25805@magnolia \
--to=darrick.wong@oracle.com \
--cc=cmaiolino@redhat.com \
--cc=linux-xfs@vger.kernel.org \
/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