From: raulhp <raulhp@ugr.es>
To: <drbd-dev@lists.linbit.com>
Subject: Re: [Drbd-dev] Protocol C
Date: Wed, 04 Jun 2014 12:21:39 +0200 [thread overview]
Message-ID: <eda7b0a7aee164c000e21bc0ff82ec64@ugr.es> (raw)
In-Reply-To: <20140530131752.GC12754@soda.linbit>
It´s correct, Thanks Lars,
Regards,
Ra
El 2014-05-30 15:17, Lars Ellenberg escribió:
> On Fri, May 30, 2014 at 12:28:19PM +0200, raulhp wrote:
>> >>>Am I misunderstanding your question?
>> >>You understand my question :-) only y want to understand how to
>> use
>> >>existing code of ACK for multicast
>> >
>> >I don't think it works that way.
>>
>> Now, What do you think?
>
> I think, amoung other things, we have some a nice language barrier
> here.
>
> I think, as I tried to explain,
> that you need to distinguish between what happens
> on the DRBD protocol level, and what happens
> on the communication transport level.
> The latter is what you are working on.
> You can do almost whatever you want there.
>
> But it should be obvious that you cannot re-use the
> DRBD protocol level "my-disk-has-failed-I-am-so-sorry" message
> to mean, on the transport layer,
> "please-resend-all-requests-I-did-miss", just because both
> concepts use the term "nack" somewhere in the description.
>
> Different things.
> Both needed.
> Not directly related.
prev parent reply other threads:[~2014-06-04 10:21 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
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 [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=eda7b0a7aee164c000e21bc0ff82ec64@ugr.es \
--to=raulhp@ugr.es \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox