All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Caulfield <pcaulfie@redhat.com>
Cc: dm-devel@redhat.com
Subject: Re: PATCH - pvmove doesn't terminate sometimes on 64-bit bigendian machines
Date: Mon, 10 Oct 2005 08:27:55 +0100	[thread overview]
Message-ID: <434A17FB.9040004@redhat.com> (raw)
In-Reply-To: <17225.56945.115400.390314@cse.unsw.edu.au>

Neil Brown wrote:
> On Wednesday September 28, agk@redhat.com wrote:
> 
>>On Wed, Sep 14, 2005 at 02:32:59PM +1000, Neil Brown wrote:
>>
>>> It is worth noting that the code uses the same bitsets for in-memory
>>> and on-disk logs.  As these bitsets are host-endian and host-sized,
>>> this means that they cannot safely be moved between computers with
>>> different architectures.  I don't know if the dm doco makes this
>>> clear...
>>
>> 
>>Are you able to try out the (untested) patch from Patrick below?
>>Since the current implementation is broken for 64-bit BE we might
>>as well fix both problems at the same time.
>>
> 
> 
> I've ask the person who reported the problem to test this patch.  I'll
> let you know what eventuates.

Thanks

> ... it's a pity about the 'ext2' appearing in there instead of a more
> sensible 'set_le_bit', isn't it :-(
> 

yes. In some (well, the big-endian) architectures it's called set_le_bit and
#defined to ext2_set_bit, bit the LE architectures just define ext2_set_bit to
be set_bit :(

-- 

patrick

      reply	other threads:[~2005-10-10  7:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-14  4:32 PATCH - pvmove doesn't terminate sometimes on 64-bit bigendian machines Neil Brown
2005-09-16 17:32 ` Alasdair G Kergon
2005-09-28 17:48 ` Alasdair G Kergon
2005-10-10  3:22   ` Neil Brown
2005-10-10  7:27     ` Patrick Caulfield [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=434A17FB.9040004@redhat.com \
    --to=pcaulfie@redhat.com \
    --cc=dm-devel@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 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.