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

Re: [PATCH 2/4] xen-blkfront: rely on the default discard granularity

To: Christoph Hellwig <hch@xxxxxx>
From: Roger Pau Monné <roger.pau@xxxxxxxxxx>
Date: Tue, 20 Feb 2024 12:50:07 +0100
Cc: Juergen Gross <jgross@xxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Oleksandr Tyshchenko <oleksandr_tyshchenko@xxxxxxxx>, Jens Axboe <axboe@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx, linux-block@xxxxxxxxxxxxxxx
Delivery-date: Tue, 20 Feb 2024 11:50:20 +0000
List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On Tue, Feb 20, 2024 at 09:49:33AM +0100, Christoph Hellwig wrote:
> The block layer now sets the discard granularity to the physical
> block size default.  Take advantage of that in xen-blkfront and only
> set the discard granularity if explicitly specified.
> 
> Signed-off-by: Christoph Hellwig <hch@xxxxxx>

Acked-by: Roger Pau Monné <roger.apu@xxxxxxxxxx>

Thanks, Roger.

References:
- convert xen-blkfront to atomic queue limit updates
  - From: Christoph Hellwig
- [PATCH 2/4] xen-blkfront: rely on the default discard granularity
  - From: Christoph Hellwig

Prev by Date: Re: [PATCH 1/4] xen-blkfront: set max_discard/secure erase limits to UINT_MAX
Next by Date: Re: [PATCH 2/2] almost fully ignore zero-size flush requests
Previous by thread: [PATCH 2/4] xen-blkfront: rely on the default discard granularity
Next by thread: [PATCH 3/4] xen-blkfront: don't redundantly set max_sements in blkif_recover
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.