From: "Theodore Ts'o" <tytso@mit.edu>
To: Yangtao Li <frank.li@vivo.com>
Cc: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk
Subject: Re: [PATCH] ext4: convert to DIV_ROUND_UP() in mpage_process_page_bufs()
Date: Fri, 10 Mar 2023 18:21:07 -0500 [thread overview]
Message-ID: <20230310232107.GE860405@mit.edu> (raw)
In-Reply-To: <20230310060734.8780-1-frank.li@vivo.com>
On Fri, Mar 10, 2023 at 02:07:34PM +0800, Yangtao Li wrote:
> Just for better readability, no code logic change.
All aside from the arguments over performance, I'm not at *all*
convinced by the "it's more readable" argument.
So yeah, let's not. We have i_blkbits for a reason, and it's because
shifting right is just simpler and easier.
BTW, doing a 64-bit division on a 32-bit platforms causes compile
failures, which was the cause of the test bot complaint:
ld: fs/ext4/inode.o: in function `mpage_process_page_bufs':
>> inode.c:(.text+0xbda): undefined reference to `__divdi3'
On 32-bit platforms --- i386 in particular --- the 64-bit division
results in an out-of-line call to a helper function that is not
supplied in the kernel compilation environment, so not only is it
slower, it Just Doesn't Work.
- Ted
next prev parent reply other threads:[~2023-03-10 23:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 6:07 [PATCH] ext4: convert to DIV_ROUND_UP() in mpage_process_page_bufs() Yangtao Li
2023-03-10 6:17 ` Eric Biggers
2023-03-10 6:27 ` Yangtao Li
2023-03-10 6:27 ` Yangtao Li
2023-03-10 6:35 ` Gao Xiang
2023-03-10 6:35 ` Gao Xiang
2023-03-10 6:37 ` Gao Xiang
2023-03-10 6:37 ` Gao Xiang
2023-03-10 6:41 ` Eric Biggers
2023-03-10 6:41 ` Eric Biggers
2023-03-10 6:37 ` Al Viro
2023-03-10 6:43 ` Al Viro
2023-03-10 6:43 ` Eric Biggers
2023-03-10 6:46 ` Al Viro
2023-03-10 6:54 ` Eric Biggers
2023-03-10 7:05 ` Al Viro
2023-03-10 7:12 ` Al Viro
2023-03-10 21:47 ` Eric Biggers
2023-03-10 19:07 ` kernel test robot
2023-03-10 19:38 ` kernel test robot
2023-03-10 23:21 ` Theodore Ts'o [this message]
2023-03-13 9:25 ` David Laight
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=20230310232107.GE860405@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=frank.li@vivo.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.