From: Vasily Averin <vasily.averin@linux.dev>
To: Sergey Senozhatsky <senozhatsky@chromium.org>,
Minchan Kim <minchan@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-block@vger.kernel.org
Subject: question about ZRAM_HUGE flag
Date: Mon, 6 Nov 2023 23:20:30 +0300 [thread overview]
Message-ID: <b6f134e7-cc2f-49f2-8c52-8ff0bacc3941@linux.dev> (raw)
ZRAM_HUGE flag doubles most significant bit in zram size.
I had an idea to redefine it, but do not fully understand how to do it correctly.
I'm sure that MSB = PAGE_SHIFT on BIG_ENDIAN but do not understand what's happen on LITTLE_ENDIAN?
Is MSB = 0 in this case? Could it have some other unpredictable value?
In any case I think we can always replace ZRAM_HUGE bit check by BIT(PAGE_SHIFT) test.
Thank you,
Vasily Averin
reply other threads:[~2023-11-06 20:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b6f134e7-cc2f-49f2-8c52-8ff0bacc3941@linux.dev \
--to=vasily.averin@linux.dev \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=senozhatsky@chromium.org \
/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
all inboxes | Powered by JetHome®