From: Ingo Molnar <mingo@kernel.org>
To: Josef Bacik <josef@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org,
torvalds@linux-foundation.org, liubo2009@cn.fujitsu.com
Subject: Re: [PATCH] Btrfs: fix 64 bit divide problem
Date: Sun, 21 Aug 2011 09:19:55 +0200 [thread overview]
Message-ID: <20110821071951.GA4013@kernel.org> (raw)
In-Reply-To: <1313843391-3904-1-git-send-email-josef@redhat.com>
* Josef Bacik <josef@redhat.com> wrote:
> This fixes a regression introduced by
>
> cdcb725c05fe0cb71777c66ddc2445fedbbb3c59
>
> In cases where we need to divide/multiply by 2 we should just left/right shift
> respectively, and in cases where theres N number of devices use do_div. Also
> make the counters u64 to match up with rw_devices. Thanks,
>
> Signed-off-by: Josef Bacik <josef@redhat.com>
Acked-and-tested-by: Ingo Molnar <mingo@elte.hu>
Thanks,
Ingo
prev parent reply other threads:[~2011-08-21 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-20 12:29 [PATCH] Btrfs: fix 64 bit divide problem Josef Bacik
2011-08-21 7:19 ` Ingo Molnar [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=20110821071951.GA4013@kernel.org \
--to=mingo@kernel.org \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liubo2009@cn.fujitsu.com \
--cc=torvalds@linux-foundation.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).