linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Coly Li <colyli@suse.de>
To: Zhen Lei <thunder.leizhen@huawei.com>,
	Jens Axboe <axboe@kernel.dk>,
	Kent Overstreet <kent.overstreet@gmail.com>,
	Alasdair Kergon <agk@redhat.com>,
	Mike Snitzer <snitzer@redhat.com>, dm-devel <dm-devel@redhat.com>,
	linux-block <linux-block@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-bcache <linux-bcache@vger.kernel.org>
Subject: Re: [PATCH 1/1] block: move the PAGE_SECTORS definition into <linux/blkdev.h>
Date: Fri, 21 Aug 2020 12:11:13 +0800	[thread overview]
Message-ID: <b4643e74-aad9-385f-01f2-f8e48ba4dbef@suse.de> (raw)
In-Reply-To: <20200821020345.3358-1-thunder.leizhen@huawei.com>

On 2020/8/21 10:03, Zhen Lei wrote:
> There are too many PAGE_SECTORS definitions, and all of them are the
> same. It looks a bit of a mess. So why not move it into <linux/blkdev.h>,
> to achieve a basic and unique definition.
> 
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>


A lazy question about page size > 4KB: currently in bcache code the
sector size is assumed to be 512 sectors, if kernel page > 4KB, it is
possible that PAGE_SECTORS in bcache will be a number > 8 ?

Thanks.

Coly Li


> ---
>  drivers/block/brd.c           | 1 -
>  drivers/block/null_blk_main.c | 1 -
>  drivers/md/bcache/util.h      | 2 --
>  include/linux/blkdev.h        | 5 +++--
>  include/linux/device-mapper.h | 1 -
>  5 files changed, 3 insertions(+), 7 deletions(-)
> 

[snipped]

> diff --git a/drivers/md/bcache/util.h b/drivers/md/bcache/util.h
> index c029f7443190805..55196e0f37c32c6 100644
> --- a/drivers/md/bcache/util.h
> +++ b/drivers/md/bcache/util.h
> @@ -15,8 +15,6 @@
>  
>  #include "closure.h"
>  
> -#define PAGE_SECTORS		(PAGE_SIZE / 512)
> -
>  struct closure;
>  
>  #ifdef CONFIG_BCACHE_DEBUG
> diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
> index bb5636cc17b91a7..b068dfc5f2ef0ab 100644
> --- a/include/linux/blkdev.h
> +++ b/include/linux/blkdev.h
> @@ -949,11 +949,12 @@ static inline struct request_queue *bdev_get_queue(struct block_device *bdev)
>   * multiple of 512 bytes. Hence these two constants.
>   */
>  #ifndef SECTOR_SHIFT
> -#define SECTOR_SHIFT 9
> +#define SECTOR_SHIFT		9
>  #endif
>  #ifndef SECTOR_SIZE
> -#define SECTOR_SIZE (1 << SECTOR_SHIFT)
> +#define SECTOR_SIZE		(1 << SECTOR_SHIFT)
>  #endif
> +#define PAGE_SECTORS		(PAGE_SIZE / SECTOR_SIZE)
>  
>  /*
>   * blk_rq_pos()			: the current sector
[snipped]

  reply	other threads:[~2020-08-21  4:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-21  2:03 [PATCH 1/1] block: move the PAGE_SECTORS definition into <linux/blkdev.h> Zhen Lei
2020-08-21  4:11 ` Coly Li [this message]
2020-08-21  6:48   ` Leizhen (ThunderTown)
2020-08-21  7:05     ` Coly Li
2020-09-07  7:39       ` Leizhen (ThunderTown)
2020-11-20  1:27         ` John Dorminy
2020-11-20  2:25           ` Leizhen (ThunderTown)

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=b4643e74-aad9-385f-01f2-f8e48ba4dbef@suse.de \
    --to=colyli@suse.de \
    --cc=agk@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=dm-devel@redhat.com \
    --cc=kent.overstreet@gmail.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=snitzer@redhat.com \
    --cc=thunder.leizhen@huawei.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).