linux-erofs.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Kelvin Zhang <zhangkelvin@google.com>,
	linux-erofs mailing list <linux-erofs@lists.ozlabs.org>,
	Miao Xie <miaoxie@huawei.com>, Fang Wei <fangwei1@huawei.com>
Subject: Re: [PATCH v1 2/2] Allow developer to manually set a max block size
Date: Wed, 31 May 2023 07:51:50 +0800	[thread overview]
Message-ID: <1793dc31-d1b1-e2d4-f465-e6688e78ab0b@linux.alibaba.com> (raw)
In-Reply-To: <20230530202413.2734743-2-zhangkelvin@google.com>



On 2023/5/31 04:24, Kelvin Zhang wrote:
> Signed-off-by: Kelvin Zhang <zhangkelvin@google.com>
> ---
>   include/erofs/internal.h | 2 ++
>   1 file changed, 2 insertions(+)
> 
> diff --git a/include/erofs/internal.h b/include/erofs/internal.h
> index b3d04be..6eba35d 100644
> --- a/include/erofs/internal.h
> +++ b/include/erofs/internal.h
> @@ -35,7 +35,9 @@ typedef unsigned short umode_t;
>   #define PAGE_SIZE		(1U << PAGE_SHIFT)
>   #endif
>   
> +#ifndef EROFS_MAX_BLOCK_SIZE
>   #define EROFS_MAX_BLOCK_SIZE	PAGE_SIZE
> +#endif

I have to make a configure.ac for this stuff...

Thanks,
Gao Xiang

>   
>   #define EROFS_ISLOTBITS		5
>   #define EROFS_SLOTSIZE		(1U << EROFS_ISLOTBITS)

  reply	other threads:[~2023-05-30 23:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30 20:24 [PATCH v1 1/2] Remove hardcoded block size shifts Kelvin Zhang via Linux-erofs
2023-05-30 20:24 ` [PATCH v1 2/2] Allow developer to manually set a max block size Kelvin Zhang via Linux-erofs
2023-05-30 23:51   ` Gao Xiang [this message]
2023-05-30 23:51 ` [PATCH v1 1/2] Remove hardcoded block size shifts Gao Xiang

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=1793dc31-d1b1-e2d4-f465-e6688e78ab0b@linux.alibaba.com \
    --to=hsiangkao@linux.alibaba.com \
    --cc=fangwei1@huawei.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=miaoxie@huawei.com \
    --cc=zhangkelvin@google.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).