问一个小问题

这两天郁闷得很，不知道为什么自己的程序设置成加密模式后就极大地降低了效率，所以就开始无聊的翻看DDK文档。刚刚在NDIS_PACKET_OOB_DATA中看到这样一段话：

Status
Specifies the current status of the packet descriptor and the ownership of all driver-allocated resources specified with the packet descriptor.
Only lower-level drivers and NDIS set this member.

In the Receive Path

A miniport can set this member before it calls NdisMIndicateReceivePacket to indicate how soon it needs to regain ownership of its allocated resources specified in the associated packet descriptor(s). A serialized can retrieve this value on return from NdisMIndicateReceivePacket to determine whether the resources specified with the packet descriptor for its indication can be prepared for reuse immediately. A deserialized or connection-oriented miniport, however, does not have to check this value on return from NdisMCoIndicateReceivePacket.

......

这是对该结构中Status成员的描述，联系前些日子看得关于NdisMIndicateReceivedPackets(...)中的一段文档(如下)

A deserialized miniport does not have to examine the status of indicated packets on return of NdisMIndicateReceivePacket:

If the miniport set the packet\'s Status to NDIS_STATUS_SUCCESS before indicating up the packet descriptor, the packet\'s Status is always NDIS_STATUS_PENDING on return of NdisMIndicateReceivePacket. NDIS subsequently returns the packet descriptor to the miniport\'s MiniportReturnPacket function with the packet\'s Status set to NDIS_STATUS_SUCCESS.
If the miniport set the packet\'s Status to NDIS_STATUS_RESOURCES before indicating up the packet descriptor, the packet\'s Status is always NDIS_STATUS_SUCCESS on return of NdisMIndicateReceivePacket.
......

我不禁想问两个问题：
(1)在Passthru中PtReceive函数中NdisMIndicateRecievePacket调用之后的那句

ASSERT( NDIS_GET_PACKET_STATUS(Packet) == NDIS_STATUS_RESOURCES );

有用吗？（根据上面的说明，好像没有必要吧？）
(2)NdisMIndicateReceivePacket返回的值也与文档中描述的不一样。
我做过试验，好像在这个ASSERT中把NDIS_STATUS_RESOURCE改成NDIS_STATUS_SUCCESS，程序就会出错，这和前面的在NdisMIndicateReceivePacket中描述的不一样呀！？

这两天郁闷得很，不知道为什么自己的程序设置成加密模式后就极大地降低了效率，所以就开始无聊的翻看DDK文档。刚刚在NDIS_PACKET_OOB_DATA中看到这样一段话：
[quote]
Status
Specifies the current status of the packet descriptor and the ownership of all driver-allocated resources specified with the packet descriptor.
Only lower-level drivers and NDIS set this member.

In the Receive Path

A miniport can set this member before it calls NdisMIndicateReceivePacket to indicate how soon it needs to regain ownership of its allocated resources specified in the associated packet descriptor(s). A serialized can retrieve this value on return from NdisMIndicateReceivePacket to determine whether the resources specified with the packet descriptor for its indication can be prepared for reuse immediately. A deserialized or connection-oriented miniport, however, does not have to check this value on return from NdisMCoIndicateReceivePacket.

......

这是对该结构中Status成员的描述，联系前些日子看得关于NdisMIndicateReceivedPackets(...)中的一段文档(如下)

A deserialized miniport does not have to examine the status of indicated packets on return of NdisMIndicateReceivePacket:

If the miniport set the packet\'s Status to NDIS_STATUS_SUCCESS before indicating up the packet descriptor, the packet\'s Status is always NDIS_STATUS_PENDING on return of NdisMIndicateReceivePacket. NDIS subsequently returns the packet descriptor to the miniport\'s MiniportReturnPacket function with the packet\'s Status set to NDIS_STATUS_SUCCESS.
If the miniport set the packet\'s Status to NDIS_STATUS_RESOURCES before indicating up the packet descriptor, the packet\'s Status is always NDIS_STATUS_SUCCESS on return of NdisMIndicateReceivePacket.
......

我不禁想问两个问题：
(1)在Passthru中PtReceive函数中NdisMIndicateRecievePacket调用之后的那句

ASSERT( NDIS_GET_PACKET_STATUS(Packet) == NDIS_STATUS_RESOURCES );

有用吗？（根据上面的说明，好像没有必要吧？）
(2)NdisMIndicateReceivePacket返回的值也与文档中描述的不一样。
我做过试验，好像在这个ASSERT中把NDIS_STATUS_RESOURCE改成NDIS_STATUS_SUCCESS，程序就会出错，这和前面的在NdisMIndicateReceivePacket中描述的不一样呀！？ [/quote]

那个assert有意义。
关于为什么这个assert有意义，请参看我前面的贴子，我
曾经非常详尽的解释了这个问题（一个关于何时调用receive
何时调用receivepacket的问题，和这个ndis_resource有
非常密切的关系）