All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, Pei Zhang <pezhang@redhat.com>,
	Miklos Szeredi <miklos@szeredi.hu>,
	linux-unionfs@vger.kernel.org
Subject: Re: [PATCH] block: loop: set discard_granularity as PAGE_SIZE if sb->s_blocksize is 0
Date: Mon, 24 Jan 2022 08:36:42 -0500	[thread overview]
Message-ID: <Ye6rajfXFMwOBVtR@redhat.com> (raw)
In-Reply-To: <20220124100628.1327718-1-ming.lei@redhat.com>

On Mon, Jan 24, 2022 at 06:06:28PM +0800, Ming Lei wrote:
> If backing file's filesystem has implemented ->fallocate(), we think the
> loop device can support discard, then pass sb->s_blocksize as
> discard_granularity. However, some underlying FS, such as overlayfs,
> doesn't set sb->s_blocksize, and causes discard_granularity to be set as
> zero, then the warning in __blkdev_issue_discard() is triggered.

[ Copying linux-unionfs and Miklos ]

Miklos mentioned that it might be ok to copy upper->s_blocksize into
ovl->s_blocksize in overlayfs as other anonymous filesystem set it to
some value (nfs, 9p, fuse, cifs) as well.

So it might be reasonable to fix overlayfs as well. But I think we need
a block layer fix as well to deal with any filesystem which supports
->fallocate() and does not advertize ->s_blocksize. Not advertizing
->s_blocksize will probably only lead to suboptimial performance and
nothing more.

> 
> Fix the issue by setting discard_granularity as PAGE_SIZE in this case
> since PAGE_SIZE is the most common data unit for FS.
> 
> Cc: Vivek Goyal <vgoyal@redhat.com>
> Reported-by: Pei Zhang <pezhang@redhat.com>
> Signed-off-by: Ming Lei <ming.lei@redhat.com>

Acked-by: Vivek Goyal <vgoyal@redhat.com>

Vivek

> ---
>  drivers/block/loop.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/drivers/block/loop.c b/drivers/block/loop.c
> index b1b05c45c07c..8c15bfab7e1a 100644
> --- a/drivers/block/loop.c
> +++ b/drivers/block/loop.c
> @@ -776,6 +776,10 @@ static void loop_config_discard(struct loop_device *lo)
>  	} else {
>  		max_discard_sectors = UINT_MAX >> 9;
>  		granularity = inode->i_sb->s_blocksize;
> +
> +		/* Take PAGE_SIZE if the FS doesn't provide us one hint */
> +		if (!granularity)
> +			granularity = PAGE_SIZE;
>  	}
>  
>  	if (max_discard_sectors) {
> -- 
> 2.31.1
> 


  reply	other threads:[~2022-01-24 13:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24 10:06 [PATCH] block: loop: set discard_granularity as PAGE_SIZE if sb->s_blocksize is 0 Ming Lei
2022-01-24 13:36 ` Vivek Goyal [this message]
2022-01-24 14:05 ` Christoph Hellwig
2022-01-24 15:22   ` Vivek Goyal

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=Ye6rajfXFMwOBVtR@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=ming.lei@redhat.com \
    --cc=pezhang@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.