From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: lsf-pc@lists.linux-foundation.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-xfs <linux-xfs@vger.kernel.org>,
linux-block@vger.kernel.org, martin.petersen@oracle.com,
Allison Collins <allison.henderson@oracle.com>,
bob.liu@oracle.com
Subject: Re: [LSF/MM/BPF TOPIC] selectively cramming things onto struct bio
Date: Fri, 31 Jan 2020 15:04:11 -0500 [thread overview]
Message-ID: <20200131200411.GF332835@mit.edu> (raw)
In-Reply-To: <20200131004447.GA6869@magnolia>
On Thu, Jan 30, 2020 at 04:44:47PM -0800, Darrick J. Wong wrote:
> Hi everyone,
>
> Several months ago, there was a discussion[1] about enhancing XFS to
> take a more active role in recoverying damaged blocks from a redundant
> storage device when the block device doesn't signal an error but the
> filesystem can tell that something is wrong.
>
> Yes, we (XFS) would like to be able to exhaust all available storage
> redundancy before we resort to rebuilding lost metadata, and we'd like
> to do that without implementing our own RAID layer.
>
> In the end, the largest stumbling block seems to be how to attach
> additional instructions to struct bio. Jens rejected the idea of adding
> more pointers or more bytes to a struct bio since we'd be forcing
> everyone to pay the extra memory price for a feature that in the ideal
> situation will be used infrequently.
I'd be interested in this discussion as well; the issue came up when
adding support for hardware-based inline-crypto support.
- Ted
prev parent reply other threads:[~2020-01-31 20:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 0:44 [LSF/MM/BPF TOPIC] selectively cramming things onto struct bio Darrick J. Wong
2020-01-31 20:04 ` Theodore Y. Ts'o [this message]
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=20200131200411.GF332835@mit.edu \
--to=tytso@mit.edu \
--cc=allison.henderson@oracle.com \
--cc=bob.liu@oracle.com \
--cc=darrick.wong@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).