From: Randy Dunlap <randy.dunlap@oracle.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH] blkio-throttle: Fix linux-next compilation failure on i386
Date: Tue, 28 Sep 2010 13:15:21 -0700 [thread overview]
Message-ID: <4CA24CD9.8090202@oracle.com> (raw)
In-Reply-To: <20100928193446.GE8950@redhat.com>
On 09/28/10 12:34, Vivek Goyal wrote:
> Hi Jens,
>
> One more fix for throttling logic. After this fix I realized that there is
> potential for integer overflow in my calculations. I need to figure out
> how to take care of these overflow situations and will post a patch for
> that later.
>
> Thanks
> Vivek
>
> o Randy Dunlap reported following linux-next failure. This patch fixes it.
>
> on i386:
>
> blk-throttle.c:(.text+0x1abb8): undefined reference to `__udivdi3'
> blk-throttle.c:(.text+0x1b1dc): undefined reference to `__udivdi3'
>
> o bytes_per_second interface is 64bit and I was continuing to do 64 bit
> division even on 32bit platform without help of special macros/functions
> hence the failure.
>
> Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
Thanks.
> ---
> block/blk-throttle.c | 16 ++++++++++------
> 1 file changed, 10 insertions(+), 6 deletions(-)
>
> Index: linux-2.6-block/block/blk-throttle.c
> ===================================================================
> --- linux-2.6-block.orig/block/blk-throttle.c 2010-09-28 12:42:51.000000000 -0400
> +++ linux-2.6-block/block/blk-throttle.c 2010-09-28 14:16:05.000000000 -0400
> @@ -378,7 +378,8 @@ throtl_slice_used(struct throtl_data *td
> static inline void
> throtl_trim_slice(struct throtl_data *td, struct throtl_grp *tg, bool rw)
> {
> - unsigned long nr_slices, bytes_trim, time_elapsed, io_trim;
> + unsigned long nr_slices, time_elapsed, io_trim;
> + u64 bytes_trim, tmp;
>
> BUG_ON(time_before(tg->slice_end[rw], tg->slice_start[rw]));
>
> @@ -396,8 +397,10 @@ throtl_trim_slice(struct throtl_data *td
>
> if (!nr_slices)
> return;
> + tmp = tg->bps[rw] * throtl_slice * nr_slices;
> + do_div(tmp, HZ);
> + bytes_trim = tmp;
>
> - bytes_trim = (tg->bps[rw] * throtl_slice * nr_slices)/HZ;
> io_trim = (tg->iops[rw] * throtl_slice * nr_slices)/HZ;
>
> if (!bytes_trim && !io_trim)
> @@ -415,7 +418,7 @@ throtl_trim_slice(struct throtl_data *td
>
> tg->slice_start[rw] += nr_slices * throtl_slice;
>
> - throtl_log_tg(td, tg, "[%c] trim slice nr=%lu bytes=%lu io=%lu"
> + throtl_log_tg(td, tg, "[%c] trim slice nr=%lu bytes=%llu io=%lu"
> " start=%lu end=%lu jiffies=%lu",
> rw == READ ? 'R' : 'W', nr_slices, bytes_trim, io_trim,
> tg->slice_start[rw], tg->slice_end[rw], jiffies);
> @@ -462,7 +465,7 @@ static bool tg_with_in_bps_limit(struct
> struct bio *bio, unsigned long *wait)
> {
> bool rw = bio_data_dir(bio);
> - u64 bytes_allowed, extra_bytes;
> + u64 bytes_allowed, extra_bytes, tmp;
> unsigned long jiffy_elapsed, jiffy_wait, jiffy_elapsed_rnd;
>
> jiffy_elapsed = jiffy_elapsed_rnd = jiffies - tg->slice_start[rw];
> @@ -473,8 +476,9 @@ static bool tg_with_in_bps_limit(struct
>
> jiffy_elapsed_rnd = roundup(jiffy_elapsed_rnd, throtl_slice);
>
> - bytes_allowed = (tg->bps[rw] * jiffies_to_msecs(jiffy_elapsed_rnd))
> - / MSEC_PER_SEC;
> + tmp = tg->bps[rw] * jiffies_to_msecs(jiffy_elapsed_rnd);
> + do_div(tmp, MSEC_PER_SEC);
> + bytes_allowed = tmp;
>
> if (tg->bytes_disp[rw] + bio->bi_size <= bytes_allowed) {
> if (wait)
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-09-28 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 19:34 [PATCH] blkio-throttle: Fix linux-next compilation failure on i386 Vivek Goyal
2010-09-28 20:15 ` Randy Dunlap [this message]
2010-10-01 12:51 ` Jens Axboe
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=4CA24CD9.8090202@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@redhat.com \
/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