From: Lars Marowsky-Bree <lmb@suse.de>
To: Lars Ellenberg <lars.ellenberg@linbit.com>, drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] Re: drbd in linux-ha cvs
Date: Tue, 7 Sep 2004 14:03:30 +0200 [thread overview]
Message-ID: <20040907120330.GH10035@marowsky-bree.de> (raw)
In-Reply-To: <20040907104926.GA7387@nudl>
On 2004-09-07T12:49:26,
Lars Ellenberg <lars.ellenberg@linbit.com> said:
> it is more clean to have one ioctl, get the full info, and output that.
> I feel uneasy about introducing additional races by using several ioctls
> in a row (even if they all finish within one second). of course, once we
> have that info it could be stale already, but at least we have the
> guarantee that at some point in time it was correct.
Well, even if not correct, so at least it was consistent ;-)
It's also much easier to maintain in the external script, and less
likely to be gotten wrong in the script.
> as soon as we have a sane interface, I don't expect the internals to
> change so often, so the "maintenance trouble" is very low, either way.
Well, even if eventually change and export more data, that's more
maintainable.
I don't need writes to the generation counters, but getting at all that
information to know where to move things would be quite helpful.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
High Availability & Clustering \\\ ///
SUSE Labs, Research and Development \honk/
SUSE LINUX AG - A Novell company \\//
next prev parent reply other threads:[~2004-09-07 12:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040906135609.GT11820@marowsky-bree.de>
[not found] ` <20040906145237.GB28956@nudl>
2004-09-07 7:57 ` [Drbd-dev] Re: drbd in linux-ha cvs Philipp Reisner
2004-09-07 9:15 ` Lars Ellenberg
2004-09-07 9:43 ` Philipp Reisner
2004-09-07 10:49 ` Lars Ellenberg
2004-09-07 12:03 ` Lars Marowsky-Bree [this message]
2004-09-07 12:56 ` Philipp Reisner
2004-09-07 15:45 ` Lars Ellenberg
2004-09-08 11:21 ` Lars Marowsky-Bree
2004-09-07 12:54 ` Philipp Reisner
2004-09-07 9:45 ` 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=20040907120330.GH10035@marowsky-bree.de \
--to=lmb@suse.de \
--cc=drbd-dev@lists.linbit.com \
--cc=lars.ellenberg@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