From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] Protocol C
Date: Wed, 28 May 2014 00:40:53 +0200 [thread overview]
Message-ID: <20140527224053.GD17111@soda.linbit> (raw)
In-Reply-To: <065690d908f4c5aaeba8d8763c41a764@ugr.es>
On Tue, May 27, 2014 at 05:33:53PM +0200, raulhp wrote:
> Hi all,
>
> Can someone explain me how the Protocol C operate?, if the receiver
> send an ACK for every block or how ACK works.
It basically goes like this:
local:
submit to disk
+ send the data,
remote: receive the data
disk completion submit to disk
disk completion
send ack back
receive ack
complete to upper layers,
once both local disk completion
and remote ack have been seen.
With some more housekeeping to be able to detect failures,
and recover from them as gracefully as possible.
> which exactly is the source code?
exactly "most of it" ;-) sorry.
there is a lot going on, and all those various stages cannot be covered
with "look there, these six lines of code do it".
What are you trying to do?
--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
next prev parent reply other threads:[~2014-05-27 22:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 15:33 [Drbd-dev] Protocol C raulhp
2014-05-27 22:40 ` Lars Ellenberg [this message]
2014-05-28 10:14 ` raulhp
2014-05-28 11:56 ` Lars Ellenberg
2014-05-28 12:32 ` raulhp
2014-05-28 12:49 ` Lars Ellenberg
2014-05-28 15:25 ` raulhp
2014-05-28 18:36 ` Lars Ellenberg
2014-05-29 10:45 ` raulhp
2014-05-29 21:29 ` Lars Ellenberg
2014-05-30 10:28 ` raulhp
2014-05-30 13:17 ` Lars Ellenberg
2014-06-04 10:21 ` raulhp
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=20140527224053.GD17111@soda.linbit \
--to=lars.ellenberg@linbit.com \
--cc=drbd-dev@lists.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 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.