Re: Is SNP broken?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



I've asked this because several approaches are developing to accelerate
tcp/ip processing - varying from filtering and "pre-cooking" L2 packets before
they reach the OS (which uses standard drivers and IP stack), to
solutions that intercept sockets API in usermode and completely
bypass everything below it.

So if the 3rd party (or even MS) software can not cope with MS own IP
acceleration solution, are all these attempts doomed too?

Regards,
--PA


"PCAUSA" <pcausa@xxxxxxxxx> wrote in message news:b33b736e-3518-469c-ab9c-cec51006fb92@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Surely it doesn't make much sense. If the SNP is added and depends on
NDIS 5.2 miniports, then surely it should be bright enough to detect
whether NDIS 5.2 support is present. IIRC, there are OIDs for this
purpose.

Thomas F. Divine


On May 15, 7:41 pm, "Pavel A." <pave...@xxxxxxxxxxxxxxx> wrote:
Hmm. We could assume that there is a ndistest suite for TOE, and all
shipping 3rd party drivers
have passed the formal and functional tests, and also some interop testing.
I'd rather agree with Thomas, but the KB article does not say anything
about any other software, besides of MS own components (dhcp, rdp client...)

--PA

"GNR" <G...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message

news:32BE2BB2-3687-40CF-89E2-B0EDACEE1B56@xxxxxxxxxxxxxxxx> No, I think it is the other way.

> In the workarounds section, the "Method 1" says "The driver must meet
> Network Driver Interface Specification (NDIS) 5.2 or a later version of
> this
> specification."

> This means if the Network Card has NDIS 5.2 driver, it works fine and > you
> don't need to turn off SNP.

> Am I reading it right?
> --
> --GNR

> "PCAUSA" wrote:

>> On May 15, 5:58 pm, "Pavel A." <pave...@xxxxxxxxxxxxxxx> wrote:
>> > Just noticed this KB article -http://support.microsoft.com/kb/948496

>> > So what does this mean? are RSS and toe broken somewhere in NDIS or >> > IP
>> > stack, or the issues are caused by netcard drivers?

>> > Regards,
>> > --PA
>> Pavel,

>> I think that this is saying:

>> IF you have TCP/IP Offload-enabled network adapter, then there is a
>> lot of software that doesn't know how to deal with TOE adapters with
>> the SNP. In fact, some TOE operations are implemented using a TCP/Ip
>> engine in the adapter itself and may not even be observable by various
>> filters. Hence - they break.

>> If you want the features of the non-TOE-aware services, then turn off
>> SNP.

>> Your thoughts?

>> Thomas F. Divine

.



Relevant Pages

  • Re: network driver and restart
    ... on packets bound to go over dial up connection? ... NDIS IM drivers can't actually layer directly over the lower-level WAM miniports. ...
    (microsoft.public.development.device.drivers)
  • Re: Running NDISTest on Vista with an NDIS IM Driver
    ... Currenty there are no logo programs or tests that test any NDIS IM drivers. ... I tried using the version that comes with WLK/DTM on PassThru (NDIS IM ... Loaded Module Info: ...
    (microsoft.public.development.device.drivers)
  • Re: How to check if a spin lock has been freed or released?
    ... >> they're writing Windows drivers, ... Both on NDIS as well as on if or how other people make ... I think you assumed that I'm a Windows driver developer. ... I said that I wrote the FreeBSD NDIS emulator (or "NDIS ...
    (microsoft.public.development.device.drivers)
  • Re: How to check if a spin lock has been freed or released?
    ... > they're writing Windows drivers, ... Both on NDIS as well as on if or how other people make ...
    (microsoft.public.development.device.drivers)
  • Re: Short question on the common use of NDIS Hooking instead of IM drivers
    ... You are correct that an IM driver is the correct approach to filter MAC level packets. ... Psuedo-IM filter drivers were common place for Windows 9x and even some software targeting NT4. ... For NT6 NDIS Ligthweight Filters are the best choice. ... many of the ndis hooks use undocumented calls/structures that may not ...
    (microsoft.public.development.device.drivers)