Re: ZwCloseHandle asynchronous on no read/write activity?
- From: dmitry.sychov@xxxxxxx
- Date: 2 Oct 2006 00:03:53 -0700
I think the FS should queue the request, ie internally delay the
actual processing of the close/cleanup IRP even with STATUS_SUCCESS
return.
and "delete-on-close" should be delayed too.
I believe this is both true for NTFS & FAT.
but this should be properly documented like it is done for other OSes.
micro optimizing one call, you can't fully peg the CPU in all paths
why not, it does not take much time anyway. :)
regards, dmitry
Doron Holan [MS] wrote:
close handle is synchronous. it sends a cleanup and possibly a close irp to
the FS. what the FS does with that is dependent on the FS. i think you are
micro optimizing one call, you can't fully peg the CPU in all paths ;)
.
- References:
- ZwCloseHandle asynchronous on no read/write activity?
- From: dmitry . sychov
- Re: ZwCloseHandle asynchronous on no read/write activity?
- From: Doron Holan [MS]
- Re: ZwCloseHandle asynchronous on no read/write activity?
- From: dmitry . sychov
- Re: ZwCloseHandle asynchronous on no read/write activity?
- From: Doron Holan [MS]
- ZwCloseHandle asynchronous on no read/write activity?
- Prev by Date: Re: Need to access Specific EHCI operational registers
- Next by Date: Re: Change device name from "Generic USB Audio Device"?
- Previous by thread: Re: ZwCloseHandle asynchronous on no read/write activity?
- Next by thread: Re: Who creates URB
- Index(es):
Relevant Pages
|
Loading