Distributed Replicated Block Device (DRBD) development
 help / color / mirror / Atom feed
From: Philipp Reisner <philipp.reisner@linbit.com>
To: drbd-dev@linbit.com
Subject: Re: [Drbd-dev] inter-arch PAGE_SIZE problem
Date: Mon, 27 Sep 2004 16:04:18 +0200	[thread overview]
Message-ID: <200409271604.18224.philipp.reisner@linbit.com> (raw)
In-Reply-To: <P3J8pVXQZJMx4eU9q8DUNEQ=lge@web.de>

Am Freitag, 24. September 2004 14:37 schrieb Lars Ellenberg:
> int drbd_make_request_26(request_queue_t *q, struct bio *bio)
> {
> ...
>   /*
>    * what we "blindly" assume:
>    */
>   D_ASSERT(bio->bi_size > 0);
>   D_ASSERT( (bio->bi_size & 0x1ff) == 0);
>   D_ASSERT(bio->bi_size <= PAGE_SIZE);
>   D_ASSERT(bio->bi_vcnt == 1);
>   D_ASSERT(bio->bi_idx == 0);
>
> oopsie.
> we are going to send PAGE_SIZE requests over the wire,
> but the other side may have a different PAGE_SIZE...
>
> // mirrored write
> int receive_Data(drbd_dev *mdev,Drbd_Header* h)
> {
> ...
>         /* I expect a block to be a multiple of 512 byte, and
>          * no more than 4K (PAGE_SIZE). is this too restrictive?
>          */
>         ERR_IF(data_size == 0) return FALSE;
>         ERR_IF(data_size &  0x1ff) return FALSE;
>         ERR_IF(data_size >  PAGE_SIZE) return FALSE;
>
>
> we need to agree to use fixed 4K, I guess.  optionally negotiate a
> higher "drbd_page_size" during the initial connection handshake.

Right. we should consider this. But I think a general high performace
solution is not neccesary, since cluster of machines with
different PAGE_SIZE are of academic interest only. (IMHO)

I think for drbd-0.8 it is sufficient to inform the user about the fact...

[...]

>
> does that all make sense?

Yes, right!

-philipp

  reply	other threads:[~2004-09-27 14:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-24 12:37 [Drbd-dev] inter-arch PAGE_SIZE problem Lars Ellenberg
2004-09-27 14:04 ` Philipp Reisner [this message]
2004-09-27 14:32   ` Lars Ellenberg

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=200409271604.18224.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