From: Neil Brown <neilb@suse.de>
To: Shaohua Li <shli@fb.com>, linux-raid@vger.kernel.org
Cc: Kernel-team@fb.com, songliubraving@fb.com, hch@infradead.org,
dan.j.williams@intel.com
Subject: Re: [PATCH 3/6] raid5-cache: add trim support for log
Date: Thu, 08 Oct 2015 12:53:47 +1100 [thread overview]
Message-ID: <87si5m6s7o.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <581084e9c46ee200f8fedf2dcfec4e897517c0ed.1443973492.git.shli@fb.com>
[-- Attachment #1: Type: text/plain, Size: 2842 bytes --]
Shaohua Li <shli@fb.com> writes:
> Since superblock is updated infrequently, we do a simple trim of log
> disk (a synchronous trim)
>
> Signed-off-by: Shaohua Li <shli@fb.com>
> ---
> drivers/md/raid5-cache.c | 38 +++++++++++++++++++++++++++++++++++++-
> 1 file changed, 37 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/md/raid5-cache.c b/drivers/md/raid5-cache.c
> index 93097a8..6c52168 100644
> --- a/drivers/md/raid5-cache.c
> +++ b/drivers/md/raid5-cache.c
> @@ -654,6 +654,42 @@ static void r5l_kick_io_unit(struct r5l_log *log)
> }
>
> static void r5l_write_super(struct r5l_log *log, sector_t cp);
> +static void r5l_write_super_and_discard_space(struct r5l_log *log,
> + sector_t end)
> +{
> + struct block_device *bdev = log->rdev->bdev;
> + struct mddev *mddev;
> +
> + r5l_write_super(log, end);
> +
> + if (!blk_queue_discard(bdev_get_queue(bdev)))
> + return;
> +
> + mddev = log->rdev->mddev;
> + if (!mddev_is_locked(mddev)) {
> + set_bit(MD_CHANGE_PENDING, &mddev->flags);
> + md_wakeup_thread(mddev->thread);
> + wait_event(mddev->sb_wait,
> + !test_bit(MD_CHANGE_PENDING, &mddev->flags));
> + } else { /* we are stopping the array, already take reconfig_mutex */
> + md_update_sb(mddev, 1);
> + }
No.
Just because mddev is locked, that doesn't mean that this thread owns
the lock. Some other thread might just happen to have it locked for a
moment, and may unlock it long before we get to md_update_sb().
If you cannot block here, then you need to find a way to schedule the
discard after the md_update_sb() has happened.
Maybe set some flag, and in raid5d(), after md_check_recovery(), see if
the superblock has been written and if the discard is still pending, and
then do the discard. Maybe.
Or pass a flag into r5l_do_reclaim() to say whether this thread holds
the lock or not.
NeilBrown
> +
> + if (log->last_checkpoint < end) {
> + blkdev_issue_discard(bdev,
> + log->last_checkpoint + log->rdev->data_offset,
> + end - log->last_checkpoint, GFP_NOIO, 0);
> + } else {
> + blkdev_issue_discard(bdev,
> + log->last_checkpoint + log->rdev->data_offset,
> + log->device_size - log->last_checkpoint,
> + GFP_NOIO, 0);
> + blkdev_issue_discard(bdev, log->rdev->data_offset, end,
> + GFP_NOIO, 0);
> + }
> +}
> +
> +
> static void r5l_do_reclaim(struct r5l_log *log)
> {
> struct r5l_io_unit *io, *last;
> @@ -709,7 +745,7 @@ static void r5l_do_reclaim(struct r5l_log *log)
> * here, because the log area might be reused soon and we don't want to
> * confuse recovery
> */
> - r5l_write_super(log, last->log_start);
> + r5l_write_super_and_discard_space(log, last->log_start);
>
> mutex_lock(&log->io_mutex);
> log->last_checkpoint = last->log_start;
> --
> 2.4.6
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2015-10-08 1:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-04 16:20 [PATCH 0/6] raid5-cache fixes Shaohua Li
2015-10-04 16:20 ` [PATCH 1/6] md: show journal for journal disk in disk state sysfs Shaohua Li
2015-10-04 16:20 ` [PATCH 2/6] raid5-cache: move reclaim stop to quiesce Shaohua Li
2015-10-04 16:20 ` [PATCH 3/6] raid5-cache: add trim support for log Shaohua Li
2015-10-08 1:53 ` Neil Brown [this message]
2015-10-04 16:20 ` [PATCH 4/6] md: don't export log device Shaohua Li
2015-10-08 1:57 ` Neil Brown
2015-10-08 3:16 ` Shaohua Li
2015-10-08 4:16 ` Neil Brown
2015-10-08 4:31 ` Shaohua Li
2015-10-08 6:04 ` Neil Brown
2015-10-13 12:07 ` Christoph Hellwig
2015-10-13 20:41 ` Neil Brown
2015-10-04 16:20 ` [PATCH 5/6] md: set In_Sync for log disk Shaohua Li
2015-10-04 16:20 ` [PATCH 6/6] raid5-cache: IO error handling Shaohua Li
2015-10-08 2:10 ` [PATCH 0/6] raid5-cache fixes Neil Brown
2015-10-08 2:56 ` Shaohua Li
2015-10-08 3:18 ` Neil Brown
2015-10-08 3:24 ` Shaohua Li
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=87si5m6s7o.fsf@notabene.neil.brown.name \
--to=neilb@suse.de \
--cc=Kernel-team@fb.com \
--cc=dan.j.williams@intel.com \
--cc=hch@infradead.org \
--cc=linux-raid@vger.kernel.org \
--cc=shli@fb.com \
--cc=songliubraving@fb.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).