Re: [PATCH v7 0/6] block/md/dm: set chunk_sectors from stacked dev stripe size

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH v7 0/6] block/md/dm: set chunk_sectors from stacked dev stripe size
From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
Date: Fri, 11 Jul 2025 07:43:50 -0400
Cc: agk@xxxxxxxxxx, snitzer@xxxxxxxxxx, mpatocka@xxxxxxxxxx, song@xxxxxxxxxx, yukuai3@xxxxxxxxxx, hch@xxxxxx, nilay@xxxxxxxxxxxxx, axboe@xxxxxxxxx, cem@xxxxxxxxxx, dm-devel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-raid@xxxxxxxxxxxxxxx, linux-block@xxxxxxxxxxxxxxx, ojaswin@xxxxxxxxxxxxx, martin.petersen@xxxxxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxxxxxx, djwong@xxxxxxxxxx, dlemoal@xxxxxxxxxx
In-reply-to: <20250711105258.3135198-1-john.g.garry@oracle.com> (John Garry's message of "Fri, 11 Jul 2025 10:52:52 +0000")
Organization: Oracle Corporation
References: <20250711105258.3135198-1-john.g.garry@oracle.com>

John,

> This value in io_min is used to configure any atomic write limit for
> the stacked device. The idea is that the atomic write unit max is a
> power-of-2 factor of the stripe size, and the stripe size is available
> in io_min.

LGTM.

Reviewed-by: Martin K. Petersen <martin.petersen@xxxxxxxxxx>

-- 
Martin K. Petersen

References:
- [PATCH v7 0/6] block/md/dm: set chunk_sectors from stacked dev stripe size
  - From: John Garry

Prev by Date: Re: refactor the iomap writeback code v5
Next by Date: Re: [PATCH v4 1/6] fs: enhance and rename shutdown() callback to remove_bdev()
Previous by thread: [PATCH v7 6/6] block: use chunk_sectors when evaluating stacked atomic write limits
Next by thread: Re: [PATCH v7 0/6] block/md/dm: set chunk_sectors from stacked dev stripe size
Index(es):
- Date
- Thread

[Index of Archives] [XFS Filesystem Development (older mail)] [Linux Filesystem Development] [Linux Audio Users] [Yosemite Trails] [Linux Kernel] [Linux RAID] [Linux SCSI]

Powered by Linux