Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-dev@linbit.com
Subject: [Drbd-dev] Fwd: Re: drbd-user post from paul.clements@steeleye.com requires approval
Date: Tue, 3 May 2005 17:58:48 +0200	[thread overview]
Message-ID: <200505031758.48886.philipp.reisner@linbit.com> (raw)
In-Reply-To: <mailman.387.1115057918.21568.drbd-user@lists.linbit.com>



----------  Weitergeleitete Nachricht  ----------

Subject: Re: drbd-user post from paul.clements@steeleye.com requires approval
Date: Dienstag, 3. Mai 2005 17:57
From: Philipp Reisner <philipp.reisner@linbit.com>
To: Paul Clements <paul.clements@steeleye.com>

Am Montag, 2. Mai 2005 20:18 schrieben Sie:
> We've recently been trying to certify DRBD (we've tried both 0.7.5 and
> 0.7.10 with the same results) on ppc64 with RHEL3.
>
> Unfortunately, we have run into two fairly serious issues:
>
> 1) we had to hack up the source just to get it to build:
>
> The basic problem is that the adjust_drbd_config_h.sh script is not
> doing the right thing for RHEL3 on ppc64. RHEL3 has a find_next_bit()
> function, and on most architectures it's an inline function. However, on
> ppc64 it's not inline and it's not exported, which means drbd (being a
> module) can't use it. So we have to actually disable the
> HAVE_FIND_NEXT_BIT setting in drbd_config.h. Also, there is no
> arch-specific find_next_bit function for ppc64 in drbd_compat_types.h,
> so we have to use the generic find_next_bit function that's in that file
> (by defining USE_GENERIC_FIND_NEXT_BIT in drbd_config.h). Of course,
> when this function is defined, it conflicts with the previous
> find_next_bit function declaration from the kernel headers
> (asm-ppc64/bitops.h). So, we had to rename the generic function to
> generic_find_next_bit and change all calls in the drbd source (just one
> in drbd_bitmap.c) to use generic_find_next_bit instead of find_next_bit.
>
>
> 2) additionally, the driver appears to start up fine on both machines,
> but when the resync begins, it quickly stalls and never makes any progress

Hi Paul,

DRBD-0.7.10 works on Linux-2.6.x based distributions on ppc64.
I guess the way to go to get it to work on 2.4 is make it to use the
ppc64 specific find_next_bit() function.

I am ready to accept a patch, and to include this into 0.7.11, but
I do not have a ppc64 machine here to do it myself.

PS: The mailing lists only allows posts from subscribed addresses.

-philipp
--

: Dipl-Ing Philipp Reisner                      Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH          Fax +43-1-8178292-82 :
: Schönbrunnerstr 244, 1120 Vienna, Austria    http://www.linbit.com :

-------------------------------------------------------

-- 
: Dipl-Ing Philipp Reisner                      Tel +43-1-8178292-50 :
: LINBIT Information Technologies GmbH          Fax +43-1-8178292-82 :
: Schönbrunnerstr 244, 1120 Vienna, Austria    http://www.linbit.com :

       reply	other threads:[~2005-05-03 15:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.387.1115057918.21568.drbd-user@lists.linbit.com>
2005-05-03 15:58 ` Philipp Reisner [this message]
     [not found] ` <4277A20A.9020309@steeleye.com>
     [not found]   ` <4277D801.1060605@steeleye.com>
2005-05-04  8:17     ` [Drbd-dev] Re: drbd-user post from paul.clements@steeleye.com requires approval Philipp Reisner

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=200505031758.48886.philipp.reisner@linbit.com \
    --to=philipp.reisner@linbit.com \
    --cc=drbd-dev@linbit.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