• <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

            導航

            統(tǒng)計

            留言簿(13)

            隨筆分類(287)

            隨筆檔案(289)

            漏洞

            搜索

            積分與排名

            最新評論

            閱讀排行榜

            久久综合伊人77777| 久久精品国产亚洲AV大全| 日本久久久久久中文字幕| 久久久青草久久久青草| 精品久久人人做人人爽综合| 久久精品国产精品亜洲毛片| 久久午夜无码鲁丝片秋霞| 久久精品国产亚洲av麻豆小说| 国产精品久久午夜夜伦鲁鲁| 韩国三级中文字幕hd久久精品 | 国产激情久久久久影院| 无码任你躁久久久久久老妇| 亚洲欧美日韩中文久久| 亚洲精品国产第一综合99久久| 久久人人爽爽爽人久久久| 久久无码AV中文出轨人妻| 一本一道久久综合狠狠老| 国产精品欧美久久久久无广告| 人人狠狠综合久久88成人| 久久精品18| 99久久99久久精品国产| 国产精品久久网| 日产精品久久久久久久性色| 香蕉久久久久久狠狠色| 国内精品免费久久影院| 久久综合丝袜日本网| 久久久久久毛片免费播放| 久久乐国产综合亚洲精品| 天天综合久久一二三区| 91久久成人免费| 久久精品国产精品亚洲人人 | 日产精品久久久一区二区| 久久国产精品无码网站| 91精品国产色综久久 | 久久亚洲国产最新网站| 久久精品一区二区三区中文字幕 | 国产成人久久久精品二区三区| 国产亚洲精品自在久久| 久久午夜伦鲁片免费无码| 久久精品亚洲中文字幕无码麻豆 | 一级做a爱片久久毛片|