The two operates at different levels of the store client code.
copy_event_pending indicates there is a storeClientCopy() call
pending for completetion.
disk_io_pending indicates there is a internal disk I/O request
pending.
The disk I/O may be triggered by storeClientCopy().
Regards
Henrik
On Sunday 21 April 2002 16:02, maer727@sohu.com wrote:
> Hi, pals!
>
> In this function, there is a flag disk_io_pending. I use
> grep -C to find the locations where the source files are
> using the flag. I also compare disk_io_pending with
> copy_event_pending. I think when dealing with memory,
> we use the flag copy_event_pending, when dealing with the
> disk, we use the flag disk_io_pending. IMHO So, we can not
> use disk_io_pending when dealing with memory and can not use
> copy_event_pending when dealing with disk. But it seems that
> sometimes copy_event_pending can also be used in disk case. maybe.
>
> But I am not very sure about it. :-)
>
> Am I correct? Please give me a simple explanation about the two
> flags. What is the difference between them?
>
> Best regards,
> George Ma
Received on Sun Apr 21 2002 - 08:32:01 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:15:17 MST