From: Mike Fedyk <mfedyk@mikefedyk.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [patch 0/2] Control filesystem balances (kernel side)
Date: Mon, 8 Nov 2010 10:01:28 -0800 [thread overview]
Message-ID: <AANLkTimeYFN-iZ9sNNJTJT7HsdeyFsio0P_AAO7sRU70@mail.gmail.com> (raw)
[ sorry for breaking the thread, I'm replying from the archives, I was
unsubbed after a mail server issue and didn't notice till now... ]
On Sat, Oct 30, 2010 at 07:44:35PM +0200, Goffredo Baroncelli wrote:
> > balance -> info on balancing
Hugo Mills wrote:
> For the one-value-per-file rule of sysfs, this should probably be
> balance_expected and balance_completed, each holding a count of block
> groups.
I'd name it balance_chunks_expected and balance_chunks_completed
next reply other threads:[~2010-11-08 18:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 18:01 Mike Fedyk [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-30 0:07 [patch 0/2] Control filesystem balances (kernel side) Hugo Mills
2010-10-30 17:44 ` Goffredo Baroncelli
2010-11-01 12:58 ` Xavier Nicollet
2010-11-01 12:52 ` Tomasz Torcz
2010-11-01 13:05 ` Hugo Mills
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=AANLkTimeYFN-iZ9sNNJTJT7HsdeyFsio0P_AAO7sRU70@mail.gmail.com \
--to=mfedyk@mikefedyk.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).