From: Byongho Lee <bhlee.kernel@gmail.com>
To: dsterba@suse.cz
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: compress: put variables defined per compress type in struct to make cache friendly
Date: Wed, 14 Oct 2015 10:17:53 +0900 [thread overview]
Message-ID: <87bnc2w8n2.fsf@gmail.com> (raw)
In-Reply-To: <20151013162834.GM27761@twin.jikos.cz>
David Sterba writes:
>
>> +static struct {
>> + struct list_head idle_workspace;
>> + spinlock_t workspace_lock;
>> + int num_workspace;
>> + atomic_t alloc_workspace;
>> + wait_queue_head_t workspace_wait;
>> +} comp[BTRFS_COMPRESS_TYPES];
>
> The name became too generic, please rename it to btrfs_comp_ws.
> btrfs_comp_workspaces would be too long. I won't mind trimming the
> members to 'ws' instead of 'workspace' so this does not result in too
> wild code formatting. The use of the workspaces is localized only to the
> compression code so it will not be confusing.
Thanks for feedback.
I will prepare v2 patch applying your comment.
prev parent reply other threads:[~2015-10-14 1:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 16:13 [PATCH] btrfs: compress: put variables defined per compress type in struct to make cache friendly Byongho Lee
2015-10-13 16:28 ` David Sterba
2015-10-14 1:17 ` Byongho Lee [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=87bnc2w8n2.fsf@gmail.com \
--to=bhlee.kernel@gmail.com \
--cc=dsterba@suse.cz \
--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 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.