From: Lars Marowsky-Bree <lmb@suse.de>
To: Philipp Reisner <philipp.reisner@linbit.com>, drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] How Locking in GFS works...
Date: Fri, 8 Oct 2004 14:55:44 +0200 [thread overview]
Message-ID: <20041008125544.GO8249@marowsky-bree.de> (raw)
In-Reply-To: <200410081432.09710.philipp.reisner@linbit.com>
On 2004-10-08T14:32:09, Philipp Reisner <philipp.reisner@linbit.com> wrote:
> 3. Concurrent writes, high latency for data packets.
> The problem now is that N2 does can not detect that this was
> a concurrent write, since it got the ACK before the conflicting
> data packets comes in.
Uhm. I don't see how this can be a problem.
In this case, one write has logically happened before the other, and
from they don't overlap - the second write will simply wipe out the
first one, which seems fine?
> 5. New write while processing a write from the peer.
Sounds just like case 1.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering
SUSE Labs, Research and Development
SUSE LINUX AG - A Novell company
next prev parent reply other threads:[~2004-10-08 12:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 12:56 [Drbd-dev] How Locking in GFS works Philipp Reisner
2004-10-04 13:01 ` Lars Marowsky-Bree
2004-10-04 13:20 ` Lars Ellenberg
2004-10-04 13:41 ` Lars Marowsky-Bree
2004-10-04 13:26 ` Philipp Reisner
2004-10-04 13:49 ` Lars Marowsky-Bree
2004-10-04 14:09 ` Philipp Reisner
2004-10-04 14:17 ` Philipp Reisner
2004-10-04 15:12 ` Lars Ellenberg
2004-10-04 20:24 ` Lars Marowsky-Bree
2004-10-08 12:32 ` Philipp Reisner
2004-10-08 12:55 ` Lars Marowsky-Bree [this message]
2004-10-08 13:37 ` Philipp Reisner
2004-10-08 13:51 ` Lars Ellenberg
2004-10-11 7:12 ` Philipp Reisner
2004-10-11 10:09 ` Lars Ellenberg
2004-10-11 10:11 ` Lars Ellenberg
2004-10-11 12:28 ` Philipp Reisner
2004-10-11 12:41 ` Philipp Reisner
2004-10-05 19:37 ` Philipp Reisner
2004-10-05 19:39 ` 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=20041008125544.GO8249@marowsky-bree.de \
--to=lmb@suse.de \
--cc=drbd-dev@lists.linbit.com \
--cc=philipp.reisner@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