From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-xfs@vger.kernel.org, libor.klepac@bcom.cz,
bfoster@redhat.com, alex@zadarastorage.com, david@fromorbit.com
Subject: Re: [PATCH 1/5] xfs: add the ability to join a held buffer to a defer_ops
Date: Thu, 14 Dec 2017 08:57:19 -0800 [thread overview]
Message-ID: <20171214165719.GT19219@magnolia> (raw)
In-Reply-To: <20171214164220.GH32616@infradead.org>
On Thu, Dec 14, 2017 at 08:42:20AM -0800, Christoph Hellwig wrote:
> Looks good,
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
>
> Although I wonder if for both inodes and buffers we eventually
> want lists instead of arrays to hold the attached objects.
We will if we ever want more than two inodes/buffers held per dfops, but
for now it doesn't seem necessary (and has the same overhead for the
dfops as a list_head).
--D
> --
> 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:[~2017-12-14 16:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 3:38 [PATCH 0/5] xfs: logging fixes Darrick J. Wong
2017-12-08 3:39 ` [PATCH 1/5] xfs: add the ability to join a held buffer to a defer_ops Darrick J. Wong
2017-12-14 16:42 ` Christoph Hellwig
2017-12-14 16:57 ` Darrick J. Wong [this message]
2017-12-08 3:39 ` [PATCH 2/5] xfs: hold xfs_buf locked between shortform->leaf conversion and the addition of an attribute Darrick J. Wong
2017-12-14 16:43 ` Christoph Hellwig
2017-12-08 3:39 ` [PATCH 3/5] xfs: queue deferred rmap ops for cow staging extent alloc/free in the right order Darrick J. Wong
2017-12-21 13:31 ` Christoph Hellwig
2017-12-08 3:39 ` [PATCH 4/5] xfs: always honor OWN_UNKNOWN rmap removal requests Darrick J. Wong
2017-12-21 13:31 ` Christoph Hellwig
2017-12-08 3:39 ` [PATCH 5/5] xfs: only skip rmap owner checks for unknown-owner rmap removal Darrick J. Wong
2017-12-21 13:31 ` 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=20171214165719.GT19219@magnolia \
--to=darrick.wong@oracle.com \
--cc=alex@zadarastorage.com \
--cc=bfoster@redhat.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=libor.klepac@bcom.cz \
--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;
as well as URLs for NNTP newsgroup(s).