From: Boaz Harrosh <bharrosh@panasas.com>
To: Chris Metcalf <cmetcalf@tilera.com>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
<linux-nfs@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Dean Hildebrand <dhildebz@umich.edu>
Subject: [PATCH v3] nfs: fix a minor do_div portability issue
Date: Thu, 11 Aug 2011 13:54:28 -0700 [thread overview]
Message-ID: <4E444184.9090109@panasas.com> (raw)
In-Reply-To: <201108111938.p7BJc44U012947@farm-0002.internal.tilera.com>
On 08/11/2011 12:32 PM, Chris Metcalf wrote:
> This change modifies filelayout_get_dense_offset() to use the functions
> in math64.h and thus avoid a 32-bit platform compile error trying to
> use do_div() on an s64 type.
>
> Signed-off-by: Chris Metcalf <cmetcalf@tilera.com>
> Cc: Boaz Harrosh <bharrosh@panasas.com>
Thanks
Reviewed-by: Boaz Harrosh <bharrosh@panasas.com>
Just if you don't mind a name change. tmp => stripe_no
while at it.
---
From: Chris Metcalf <cmetcalf@tilera.com>
Subject: [PATCH v3] nfs: fix a minor do_div portability issue
This change modifies filelayout_get_dense_offset() to use the functions
in math64.h and thus avoid a 32-bit platform compile error trying to
use do_div() on an s64 type.
Signed-off-by: Chris Metcalf <cmetcalf@tilera.com>
Reviewed-by: Boaz Harrosh <bharrosh@panasas.com>
---
fs/nfs/nfs4filelayout.c | 7 ++++---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/fs/nfs/nfs4filelayout.c b/fs/nfs/nfs4filelayout.c
index e8915d4..3ecb14f 100644
--- a/fs/nfs/nfs4filelayout.c
+++ b/fs/nfs/nfs4filelayout.c
@@ -49,12 +49,13 @@ filelayout_get_dense_offset(struct nfs4_filelayout_segment *flseg,
{
u32 stripe_width = flseg->stripe_unit * flseg->dsaddr->stripe_count;
u64 stripe_no;
+ u32 rem;
offset -= flseg->pattern_offset;
- tmp = offset;
- do_div(tmp, stripe_width);
+ stripe_no = div_u64(offset, stripe_width);
+ div_u64_rem(offset, flseg->stripe_unit, &rem);
- return tmp * flseg->stripe_unit + do_div(offset, flseg->stripe_unit);
+ return stripe_no * flseg->stripe_unit + rem;
}
/* This function is used by the layout driver to calculate the
-- 1.6.5.2
next prev parent reply other threads:[~2011-08-11 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 17:56 [PATCH] nfs: fix a couple of minor portability issues Chris Metcalf
2011-08-10 22:02 ` Boaz Harrosh
2011-08-11 13:26 ` Chris Metcalf
2011-08-11 18:27 ` Boaz Harrosh
2011-08-11 19:32 ` [PATCH v2] nfs: fix a minor do_div portability issue Chris Metcalf
2011-08-11 20:54 ` Boaz Harrosh [this message]
2011-08-11 15:17 ` [PATCH] nfs: fix a couple of minor portability issues Peng Tao
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=4E444184.9090109@panasas.com \
--to=bharrosh@panasas.com \
--cc=Trond.Myklebust@netapp.com \
--cc=cmetcalf@tilera.com \
--cc=dhildebz@umich.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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