• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>

            小默

            [zz]IoCompletion

            IoCompletion

            The IoCompletion routine completes the processing of I/O operations.

            IO_COMPLETION_ROUTINE IoCompletion;

            NTSTATUS
              IoCompletion(
                __in PDEVICE_OBJECT  DeviceObject,
                __in PIRP  Irp,
                __in PVOID  Context
                )
              {...}

            Parameters

            DeviceObject
            Caller-supplied pointer to a DEVICE_OBJECT structure. This is the device object for the target device, previously created by the driver's AddDevice routine.
            Irp
            Caller-supplied pointer to an IRP structure that describes the I/O operation.
            Context
            Caller-supplied pointer to driver-specific context information, previously supplied when calling IoSetCompletionRoutine, or IoSetCompletionRoutineEx. Context information must be stored in nonpaged memory, since an IoCompletion routine can be called at DISPATCH_LEVEL (see the following Comments section).

            Return Value

            If the IoCompletion routine determines that additional processing is required for the IRP, it must return STATUS_MORE_PROCESSING_REQUIRED. For more information, see the following Comments section. Otherwise it should return STATUS_SUCCESS. (The I/O manager only checks for the presence or absence of STATUS_MORE_PROCESSING_REQUIRED.)

            Comments

            A driver's IoCompletion routine executes in an arbitrary thread or DPC context, and at an IRQL that is less than or equal to DISPATCH_LEVEL. Because code written to execute at DISPATCH_LEVEL will also execute at lower levels, IoCompletion routines should be designed for execution at DISPATCH_LEVEL. However, because these routines are not guaranteed to run at DISPATCH_LEVEL, they must not call system routines that actually require execution at DISPATCH_LEVEL. (For more information about IRQLs, see Managing Hardware Priorities.)

            To register an IoCompletion routine for a specific IRP, a driver must call IoSetCompletionRoutine or IoSetCompletionRoutineEx, which stores the IoCompletion routine's address in the next-lower driver's I/O stack location. (Thus, a lowest-level driver cannot register an IoCompletion routine.) A driver typically calls IoSetCompletionRoutine or IoSetCompletionRoutineEx from one of its dispatch routines, each time an IRP is received. Most drivers, including all PnP drivers, can use IoSetCompletionRoutine to register their IoCompletion routine. Non-PnP drivers that may be unloaded before their IoCompletion routine executes should use IoSetCompletionRoutineEx instead.

            When any driver completes an IRP, it calls IoCompleteRequest, which in turn calls the IoCompletion routine of each higher-level driver, from the next-highest to the highest, until all higher IoCompletion routines have been called or until one routine returns STATUS_MORE_PROCESSING_REQUIRED.

            When you create the IRP, allocate a stack location for the current driver as well as any lower drivers. If you do not allocate sufficient stack locations, the DeviceObject pointer might be set to NULL when the completion routine is called. You can avoid allocating extra stack location for the current driver if you use the Context field to pass information to IoCompletion rather then relying on the DeviceObject parameter.

            If an IoCompletion routine returns STATUS_MORE_PROCESSING_REQUIRED, the lower driver's call to IoCompleteRequest immediately returns. In this case, a higher-level driver will have to call IoCompleteRequest to complete the IRP.

            For more information about implementing IoCompletion routines, see Completing IRPs.

            Example

            To define an IoCompletion callback routine that is named MyIoCompletion, you must first provide a function declaration that Static Driver Verifier (SDV) and other verification tools require, as follows:

            IO_COMPLETION_ROUTINE MyIoCompletion;

             

            Then, implement your callback routine as follows:

            NTSTATUS
              MyIoCompletion(
                __in PDEVICE_OBJECT  DeviceObject,
                __in PIRP  Irp,
                __in PVOID  Context
                )
              {
                  // Function body
              }

             

            The IO_COMPLETION_ROUTINE function type is defined in the Wdm.h header file. For more information about SDV requirements for function declarations, see Declaring Functions Using Function Role Types for WDM Drivers.

            Requirements

            IRQL: <=DISPATCH_LEVEL (see Comments section)

            Headers: Declared in Wdm.h. Include Wdm.h, Ntddk.h, or Ntifs.h.

            posted on 2009-12-29 11:36 小默 閱讀(481) 評論(0)  編輯 收藏 引用 所屬分類: Windows

            導航

            統計

            留言簿(13)

            隨筆分類(287)

            隨筆檔案(289)

            漏洞

            搜索

            積分與排名

            最新評論

            閱讀排行榜

            久久美女网站免费| 嫩草伊人久久精品少妇AV| 色成年激情久久综合| 久久99国产精品成人欧美| 色婷婷综合久久久久中文字幕| 伊人久久大香线蕉综合网站| 国内精品综合久久久40p| AV无码久久久久不卡网站下载| 色综合久久中文综合网| 热久久最新网站获取| 国产精品欧美久久久天天影视| 国产精品伦理久久久久久| 久久精品卫校国产小美女| 久久久久久久尹人综合网亚洲 | 亚洲国产一成人久久精品| 久久99国产精品久久| 久久精品一区二区三区AV| 天天久久狠狠色综合| 亚洲精品无码成人片久久| 久久精品国产WWW456C0M| 久久婷婷五月综合色高清| 97视频久久久| 欧美久久一区二区三区| 九九99精品久久久久久| 日韩久久久久久中文人妻| 久久久久久久免费视频| 国内精品伊人久久久久网站| 久久99亚洲网美利坚合众国| 少妇无套内谢久久久久| 亚洲欧美另类日本久久国产真实乱对白| 国产美女久久久| 精品乱码久久久久久久| 久久亚洲日韩精品一区二区三区| 欧美久久久久久精选9999| 久久精品成人| 久久精品国产亚洲av瑜伽| 久久国产精品免费一区| 久久亚洲天堂| 人妻无码αv中文字幕久久琪琪布| 四虎影视久久久免费| 亚洲美日韩Av中文字幕无码久久久妻妇 |