From: Sean Fu <fxinrong@gmail.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: shli@kernel.org, anton@tuxera.com, jack@suse.cz, axboe@fb.com,
ebiggers@google.com, rpeterso@redhat.com, bmarzins@redhat.com,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net
Subject: Re: [PATCH] fs: buffer: Modify alloc_page_buffers.
Date: Fri, 23 Jun 2017 16:26:25 +0800 [thread overview]
Message-ID: <20170623082622.GA31615@linux-zmni.apac.novell.com> (raw)
In-Reply-To: <20170619160315.GD10672@ZenIV.linux.org.uk>
On Mon, Jun 19, 2017 at 05:03:16PM +0100, Al Viro wrote:
> On Mon, Jun 19, 2017 at 09:01:36PM +0800, Sean Fu wrote:
> > Make alloc_page_buffers support circular buffer list and initialise
> > b_state field.
> > Optimize the performance by removing the buffer list traversal to create
> > circular buffer list.
>
> > - bh = head = alloc_page_buffers(page, blocksize, 1);
> > + bh = head = alloc_page_buffers(page, blocksize, 1, 0, 0);
>
> Frankly, I don't like that change of calling conventions; it's very easy to
> mess the order of arguments when using interfaces like that and it's hell
> to find when trying to debug the resulting mess.
>
> Do you really get an observable change in performance? What loads are
> triggering it?
Sorry for my mistake.
Infact, The time of writting a large file depends on saveral other
factors, eg system workload.
Yesterday, I tried to test the time of single calling create_empty_buffers by kretprobe
and found that the performance difference is too small to measure it.
before:
[ 944.632027] create_empty_buffers returned 878736736 and took 2160 ns
to execute
[ 944.632286] create_empty_buffers returned 878962832 and took 451 ns
to execute
[ 944.632302] create_empty_buffers returned 878962016 and took 226 ns
to execute
[ 944.632728] create_empty_buffers returned 878962832 and took 235 ns
to execute
[ 944.633105] create_empty_buffers returned 878962832 and took 167 ns
to execute
[ 944.633421] create_empty_buffers returned 878962832 and took 160 ns
to execute
after:
[39209.076519] create_empty_buffers returned 383804768 and took 1666 ns
to execute
[39209.077032] create_empty_buffers returned 383804768 and took 366 ns
to execute
[39209.077120] create_empty_buffers returned 558412336 and took 179 ns
to execute
[39209.077127] create_empty_buffers returned 558413152 and took 148 ns
to execute
[39209.077525] create_empty_buffers returned 558412336 and took 201 ns
to execute
[39209.078255] create_empty_buffers returned 814328768 and took 880 ns
to execute
[39209.078498] create_empty_buffers returned 558412336 and took 564 ns
to execute
[39209.078737] create_empty_buffers returned 558413152 and took 196 ns
to execute
This patch also complicates code.
Please ignore it.
Thanks all of you.
next prev parent reply other threads:[~2017-06-23 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 13:01 Sean Fu
2017-06-19 13:21 ` Jan Kara
2017-06-19 16:03 ` Al Viro
2017-06-21 17:07 ` Sean Fu
2017-06-23 8:26 ` Sean Fu [this message]
2017-06-19 18:20 ` kbuild test robot
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=20170623082622.GA31615@linux-zmni.apac.novell.com \
--to=fxinrong@gmail.com \
--cc=anton@tuxera.com \
--cc=axboe@fb.com \
--cc=bmarzins@redhat.com \
--cc=ebiggers@google.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=linux-raid@vger.kernel.org \
--cc=rpeterso@redhat.com \
--cc=shli@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 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®