|Subject:||Delivered state of DMAPI Event|
|From:||"Michael Li (gmail)" <mikore.li@xxxxxxxxx>|
|Date:||Wed, 12 Jul 2006 22:22:09 +0800|
|Domainkey-signature:||a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:content-type:content-transfer-encoding; b=SCoZD2TU7lcdFWquQYR7+1chWPMSb2k47/NUkNvFAbb1VSJr3CuLVc72phUwNFRs6RkfBTD3dlRJ0xloN+OOatDMr/QiumMDPxpmmp9PwkEz7bTGHFxoed/0Vf5/hmhpiSeXeRyHHs8I82rCZuLoi0O610Fc6B8w4laU0JWPRcw=|
|User-agent:||Mozilla Thunderbird 1.0.7 (Windows/20050923)|
As I know, DMAPI event can be in 2 states:
1) enqueued, undelivered
2) delivered and awaiting a response from the DM application.
The 2nd state also know as outstanding state for synchronous event message. I'd like to know the exact meaning of "delivered",
Does "delivered" means the DM application had call dm_get_event() on the event?
Can an event message automatically change state from 1 to 2 when it is enqueued?
Is there a list of the events that will always change state to delievered state after it is enqueued?
Thanks a lot,
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: [PATCH 4/7] xfs: add xfs_btree_check_lptr_disk, Christoph Hellwig|
|Next by Date:||Re: [PATCH] xfs: remove unused locking flags, Christoph Hellwig|
|Previous by Thread:||Raid5 Reshape Status + xfs_growfs = Success! (220.127.116.11), Justin Piszcz|
|Next by Thread:||Re: Delivered state of DMAPI Event, Dean Roehrich|
|Indexes:||[Date] [Thread] [Top] [All Lists]|