From: Dean Roehrich <dean.roehrich@sun.com>
To: xfs@oss.sgi.com
Subject: Re: DMF & DMAPI
Date: Tue, 25 Jul 2006 11:51:26 -0500 [thread overview]
Message-ID: <20060725165126.GA9392@kickball-mn.Central.Sun.COM> (raw)
In-Reply-To: <44C64704.8000301@gmail.com>
On Wed, Jul 26, 2006 at 12:29:56AM +0800, Michael Li (gmail) wrote:
> Hi, Dean and all,
>
> How does DMF using DMAPI? If I lauch a DM application to
> receive/response some data event message(read/write/truncate) on the
> same MDS on which a DMF server is running, is it possible to bother
> DMF's job? If it will happen, is there any tips to help designing such a
> DM application?
The DMAPI specification does not cover the case of having two independent
DMAPI apps that want to see the same events from the same files on the same
filesystem. Does that scenario even make sense when you consider the problem
that DMAPI was intended to solve?
Dean
next prev parent reply other threads:[~2006-07-25 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 16:29 DMF & DMAPI Michael Li (gmail)
2006-07-25 16:51 ` Dean Roehrich [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-26 4:24 Michael Li (Gmail)
2006-07-26 15:39 ` Dean Roehrich
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=20060725165126.GA9392@kickball-mn.Central.Sun.COM \
--to=dean.roehrich@sun.com \
--cc=xfs@oss.sgi.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