From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] Re: drbd in linux-ha cvs
Date: Tue, 7 Sep 2004 17:45:57 +0200 [thread overview]
Message-ID: <20040907154557.GA12927@nudl> (raw)
In-Reply-To: <200409071456.19233.philipp.reisner@linbit.com>
On Tue, Sep 07, 2004 at 02:56:19PM +0200, Philipp Reisner wrote:
> On Tuesday 07 September 2004 14:03, Lars Marowsky-Bree wrote:
> > 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.
> >
>
> My initial understanding was that this read-generation counters
> operation would read it off the disk (== run while the DRBD
> module is not loaded). Do you mean that ? Or do you want to have
> an ioctl to ask the module for the current value of the countes ?
I think both ways make sense.
yes, I already added __u32 gen_cnt[5] to get_config here, but
I won't commit that too soon, I have some more suggestions in the ioctl
area, so we should wait for end of September first...
lge
next prev parent reply other threads:[~2004-09-07 15:45 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
2004-09-07 12:56 ` Philipp Reisner
2004-09-07 15:45 ` Lars Ellenberg [this message]
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=20040907154557.GA12927@nudl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox