From: Alex Zarochentsev <zam@namesys.com>
To: Isaac Chanin <chanin@WPI.EDU>
Cc: reiserfs-list@namesys.com
Subject: Re: AMD64 progress?
Date: Mon, 7 Feb 2005 16:29:35 +0300 [thread overview]
Message-ID: <20050207132934.GA7482@backtop.namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0501152102230.10167-100000@ccc7.wpi.edu>
[-- Attachment #1: Type: text/plain, Size: 551 bytes --]
Hello,
On Sat, Jan 15, 2005 at 09:26:01PM -0500, Isaac Chanin wrote:
>
> Also tested this patch, similar results as to what I've been getting -
> ie. working for awhile (more than a few hours even this time, but that
> could just be coincidence, i suppose) and then going down with the normal
> reiser4_find_next_zero_bit(bnode_working_data(bnode), end_offset,
> start_offset) >= end_offset error. For the exact message see
> http://users.wpi.edu/~chanin/r4newpatch.txt.
>
please try attached patch (it is for fs/reiser4 subtree)
--
Alex.
[-- Attachment #2: bitmap-amd64-fix-2.diff --]
[-- Type: text/plain, Size: 590 bytes --]
===== plugin/space/bitmap.c 1.186 vs edited =====
--- 1.186/plugin/space/bitmap.c Wed Jan 19 18:52:52 2005
+++ edited/plugin/space/bitmap.c Mon Feb 7 16:18:37 2005
@@ -165,7 +165,7 @@
static int
find_next_zero_bit_in_word(ulong_t word, int start_bit)
{
- ulong_t mask = 1 << start_bit;
+ ulong_t mask = 1UL << start_bit;
int i = start_bit;
while ((word & mask) != 0) {
@@ -235,7 +235,7 @@
assert ("zam-965", start_bit < BITS_PER_LONG);
assert ("zam-966", start_bit >= 0);
- bit_mask = (1 << nr);
+ bit_mask = (1UL << nr);
while (bit_mask != 0) {
if (bit_mask & word)
next prev parent reply other threads:[~2005-02-07 13:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 5:33 AMD64 progress? Jake Maciejewski
2005-01-14 0:03 ` David Masover
2005-01-14 20:17 ` Alex Zarochentsev
2005-01-14 22:58 ` Jake Maciejewski
2005-01-16 2:26 ` Isaac Chanin
2005-02-07 13:29 ` Alex Zarochentsev [this message]
2005-02-07 19:34 ` Jake Maciejewski
2005-02-07 19:51 ` Alex Zarochentsev
2005-02-08 18:25 ` Jake Maciejewski
2005-02-08 19:12 ` Alex Zarochentsev
2005-02-08 20:49 ` Jake Maciejewski
2005-02-08 20:29 ` Isaac Chanin
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=20050207132934.GA7482@backtop.namesys.com \
--to=zam@namesys.com \
--cc=chanin@WPI.EDU \
--cc=reiserfs-list@namesys.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 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.