From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: Filipe David Borba Manana <fdmanana@gmail.com>,
<linux-btrfs@vger.kernel.org>
Cc: Chris Mason <clm@fb.com>
Subject: Re: [PATCH] Btrfs: remove unused wait queue in struct extent_buffer
Date: Tue, 17 Jun 2014 14:02:37 +0900 [thread overview]
Message-ID: <539FCBED.6010600@jp.fujitsu.com> (raw)
In-Reply-To: <1402920865-3120-1-git-send-email-fdmanana@gmail.com>
Hi Filipe,
(2014/06/16 21:14), Filipe David Borba Manana wrote:
> The lock_wq wait queue is not used anywhere, therefore just remove it.
> On a x86_64 system, this reduced sizeof(struct extent_buffer) from 320
> bytes down to 296 bytes, which means a 4Kb page can now be used for
> 13 extent buffers instead of 12.
>
> Signed-off-by: Filipe David Borba Manana <fdmanana@gmail.com>
It looks good to me. This field was once removed by bd681513.
However, re-introduced in error by 727011e07c
(both are Chris's patch).
I consider it's better to fix the following comment too.
===
$ cat -n fs/btrfs/extent_io.h | grep -B 3 write_lock_wq
152 /* readers use lock_wq while they wait for the write
153 * lock holders to unlock
154 */
155 wait_queue_head_t write_lock_wq;
===
We should "s/ lock_wq / write_lock_wq /" here.
Thanks,
Satoru
> ---
> fs/btrfs/extent_io.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/fs/btrfs/extent_io.h b/fs/btrfs/extent_io.h
> index 8b63f2d..dbbea4f 100644
> --- a/fs/btrfs/extent_io.h
> +++ b/fs/btrfs/extent_io.h
> @@ -158,7 +158,6 @@ struct extent_buffer {
> * to unlock
> */
> wait_queue_head_t read_lock_wq;
> - wait_queue_head_t lock_wq;
> struct page *pages[INLINE_EXTENT_BUFFER_PAGES];
> #ifdef CONFIG_BTRFS_DEBUG
> struct list_head leak_list;
>
prev parent reply other threads:[~2014-06-17 5:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 12:14 [PATCH] Btrfs: remove unused wait queue in struct extent_buffer Filipe David Borba Manana
2014-06-17 5:02 ` Satoru Takeuchi [this message]
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=539FCBED.6010600@jp.fujitsu.com \
--to=takeuchi_satoru@jp.fujitsu.com \
--cc=clm@fb.com \
--cc=fdmanana@gmail.com \
--cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).