Does anybody know if you can use an NDIS 5.1 Intermediate driver (like a
MUX) with an NDIS 6.20 physical NIC?
Will the NDIS layer transparently transform the packet formats between NDIS
5.1 style and NDIS 6.x NBL style? I realize performance will not be optimal.
Jan
Jan,
Yes, it works just as you say. NDIS inserts adaptation layers both above and below the IM driver to perform translation between NDIS6 and NDIS5 style interfaces. The only issue I have observed thus far with doing so is that when the stack is paused, suspended, etc. then restarted, resumed that the NDIS5 IM Protocol edge is unbound (which typically causes an IM driver to stop its upper miniport edge). So upper protocols see an unbind and not, say, the PnP powerdown or the stack paused.
Good Luck,
Dave Cattley
From: xxxxx@pmatrix.com
To: xxxxx@lists.osr.com
Subject: [ntdev] NDIS 5.1 IM filter with a NDIS 6.x NIC on W2K8/W2K8R2
Date: Thu, 20 May 2010 00:06:11 -0700
Does anybody know if you can use an NDIS 5.1 Intermediate driver (like a MUX) with an NDIS 6.20 physical NIC?
Will the NDIS layer transparently transform the packet formats between NDIS 5.1 style and NDIS 6.x NBL style? I realize performance will not be optimal.
Jan
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
Jan,
NDIS5x IM works with NDIS6x miniport. I know this because we had the NDIS6x miniports way before we ported our NDIS IM to 6x hence I have seen it working. IM is always lagging because it’s not in-box.
Good luck,
Calvin
I thought of it some more…
The problems with ndis51 IM on NDIS6x nic miniports can arise if the underlying NIC supports chimney offload, RSS or VMQ(virtual machine queue). So it really depends on what you plan to do in the IM driver. I.E. you won’t be able to see IP, TCP headers for the toe’d streams.
If your IM need to interact with those “scalable networking” Windows features, you will need a NDIS6x IM.
Good luck,
Calvin
Hi Calvin,
Thanks for the input. The situation is something like a NDIS 6.x IM is being
worked on, but there is already a stable shipping 5.1 IM. The question is
should a product release, which the IM driver is just a tiny part of, be
delayed because the 6.x IM is not ready yet. I’m inclined to think a very
stable 5.1 IM would be better to ship than a not really ready 6.x IM. When
the 6.x IM is really ready, it can be rolled into a update release.
A good 6.x IM, which passes though chimney, RSS, and VMQ (and all the other
6.20 optimization) as much as possible is a LOT of work. I assume a 5.1 IM
will just report to upper layers that these features don’t exist, and
performance will be degraded over what the hardware is capable of. A NDIS
6.20 NIC layered below a NDIS 5.1 IM will function exactly like a NDIS 5.1
NIC. I assume the NDIS 5.1 to/from NDIS 6.x packet format conversion will
take a performance hit too.
Do you know of any work to standardize the WMI interfaces for NIC VLAN
support across NIC vendors? The product I work on would like to create VLAN
based virtual NIC’s, and has used a generic IM driver in the past. I’d love
to be able to just use hardware vendor’s VLAN support, and just write some
user mode code to control things through WMI. Of course there do seem to be
some (lower end) NIC vendors who don’t have any custom VLAN IM driver
support, so I might need to supply a generic IM driver even if the WMI
interfaces were standardized.
Jan
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-412035-
xxxxx@lists.osr.com] On Behalf Of xxxxx@yahoo.ca
Sent: Friday, May 21, 2010 3:23 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] NDIS 5.1 IM filter with a NDIS 6.x NIC on
W2K8/W2K8R2I thought of it some more…
The problems with ndis51 IM on NDIS6x nic miniports can arise if the
underlying NIC supports chimney offload, RSS or VMQ(virtual machine
queue). So it really depends on what you plan to do in the IM driver.
I.E. you won’t be able to see IP, TCP headers for the toe’d streams.If your IM need to interact with those “scalable networking” Windows
features, you will need a NDIS6x IM.Good luck,
Calvin
Jan,
VLAN in Windows is not well regulated (if there is regulation at all).
Starting from ndis60, MSFT did have a requirement for standardizing the INF
keyword for VLAN tag, 802.1pq such that apps can use it to configure the
NIC… but it just works for 1 VLAN as you may have known. Of course, this is
useless in a server environment. So NIC vendors targeting server market have
their own VLAN solution build into their LBFO teaming driver which is mostly
implemented as NDIS n-m MUX IM.
And yes, a sophisticated IM driver that supports active processing(not just
passive pass-through) on chimney, VMQ and RSS is a LOT of work. On the other
hand it’s good for job security. I’m not a IM specialist, I just know bare
enough to not to mess with it:)
Good luck with your project.
Calvin
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jan Bottorff
Sent: Friday, May 21, 2010 6:59 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] NDIS 5.1 IM filter with a NDIS 6.x NIC on W2K8/W2K8R2
Hi Calvin,
Thanks for the input. The situation is something like a NDIS 6.x IM is being
worked on, but there is already a stable shipping 5.1 IM. The question is
should a product release, which the IM driver is just a tiny part of, be
delayed because the 6.x IM is not ready yet. I’m inclined to think a very
stable 5.1 IM would be better to ship than a not really ready 6.x IM. When
the 6.x IM is really ready, it can be rolled into a update release.
A good 6.x IM, which passes though chimney, RSS, and VMQ (and all the other
6.20 optimization) as much as possible is a LOT of work. I assume a 5.1 IM
will just report to upper layers that these features don’t exist, and
performance will be degraded over what the hardware is capable of. A NDIS
6.20 NIC layered below a NDIS 5.1 IM will function exactly like a NDIS 5.1
NIC. I assume the NDIS 5.1 to/from NDIS 6.x packet format conversion will
take a performance hit too.
Do you know of any work to standardize the WMI interfaces for NIC VLAN
support across NIC vendors? The product I work on would like to create VLAN
based virtual NIC’s, and has used a generic IM driver in the past. I’d love
to be able to just use hardware vendor’s VLAN support, and just write some
user mode code to control things through WMI. Of course there do seem to be
some (lower end) NIC vendors who don’t have any custom VLAN IM driver
support, so I might need to supply a generic IM driver even if the WMI
interfaces were standardized.
Jan
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-412035-
xxxxx@lists.osr.com] On Behalf Of xxxxx@yahoo.ca
Sent: Friday, May 21, 2010 3:23 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] NDIS 5.1 IM filter with a NDIS 6.x NIC on
W2K8/W2K8R2I thought of it some more…
The problems with ndis51 IM on NDIS6x nic miniports can arise if the
underlying NIC supports chimney offload, RSS or VMQ(virtual machine
queue). So it really depends on what you plan to do in the IM driver.
I.E. you won’t be able to see IP, TCP headers for the toe’d streams.If your IM need to interact with those “scalable networking” Windows
features, you will need a NDIS6x IM.Good luck,
Calvin
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Err, maybe I’m not ‘up to date’ here, but I was sure that even NDIS 6.x LWF
basically means than chimney and friends goodness has to be disabled?
wrote in message news:xxxxx@ntdev…
> I thought of it some more…
>
> The problems with ndis51 IM on NDIS6x nic miniports can arise if the
> underlying NIC supports chimney offload, RSS or VMQ(virtual machine
> queue). So it really depends on what you plan to do in the IM driver. I.E.
> you won’t be able to see IP, TCP headers for the toe’d streams.
>
> If your IM need to interact with those “scalable networking” Windows
> features, you will need a NDIS6x IM.
>
> Good luck,
> Calvin
>
You can write a chimney-aware IM driver that will “pass through” the chimney capability to TCPIP.
http://msdn.microsoft.com/en-us/library/ff570931(v=VS.85).aspx
Chimney works fine in the presence of LWFs, but the LWFs don’t participate in the offload. E.g., you can’t intercept and modify offloaded TCP data streams from a LWF.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Lyndon J. Clarke
Sent: Tuesday, June 01, 2010 3:41 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] NDIS 5.1 IM filter with a NDIS 6.x NIC on W2K8/W2K8R2
Err, maybe I’m not ‘up to date’ here, but I was sure that even NDIS 6.x LWF basically means than chimney and friends goodness has to be disabled?
wrote in message news:xxxxx@ntdev…
> I thought of it some more…
>
> The problems with ndis51 IM on NDIS6x nic miniports can arise if the
> underlying NIC supports chimney offload, RSS or VMQ(virtual machine
> queue). So it really depends on what you plan to do in the IM driver. I.E.
> you won’t be able to see IP, TCP headers for the toe’d streams.
>
> If your IM need to interact with those “scalable networking” Windows
> features, you will need a NDIS6x IM.
>
> Good luck,
> Calvin
>
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
I know real advice would need to come for real legal people, but any guess
if a NDIS 6.x IM driver with Chimmney pass-thru would require a patent
license from Alacratech? I thought it was the Chimmney API covered by their
patent, and if my IM exposed that API, I might be infringing. Of course the
nic vendor below my IM must have already dealt with the patent issues, so
it’s not clear an IM driver has to deal with a license for an API that must
already be licensed.
Jan
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-413335-
xxxxx@lists.osr.com] On Behalf Of Jeffrey Tippet
Sent: Wednesday, June 02, 2010 3:56 PM
To: Windows System Software Devs Interest List
Subject: RE: Re:[ntdev] NDIS 5.1 IM filter with a NDIS 6.x NIC on
W2K8/W2K8R2You can write a chimney-aware IM driver that will “pass through” the
chimney capability to TCPIP.
http://msdn.microsoft.com/en-us/library/ff570931(v=VS.85).aspxChimney works fine in the presence of LWFs, but the LWFs don’t
participate in the offload. E.g., you can’t intercept and modify
offloaded TCP data streams from a LWF.-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-413256-
xxxxx@lists.osr.com] On Behalf Of Lyndon J. Clarke
Sent: Tuesday, June 01, 2010 3:41 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] NDIS 5.1 IM filter with a NDIS 6.x NIC on
W2K8/W2K8R2Err, maybe I’m not ‘up to date’ here, but I was sure that even NDIS 6.x
LWF basically means than chimney and friends goodness has to be
disabled?wrote in message news:xxxxx@ntdev…
> > I thought of it some more…
> >
> > The problems with ndis51 IM on NDIS6x nic miniports can arise if the
> > underlying NIC supports chimney offload, RSS or VMQ(virtual machine
> > queue). So it really depends on what you plan to do in the IM driver.
> I.E.
> > you won’t be able to see IP, TCP headers for the toe’d streams.
> >
> > If your IM need to interact with those “scalable networking” Windows
> > features, you will need a NDIS6x IM.
> >
> > Good luck,
> > Calvin
> >
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
I think what Mr. Tippet is saying is that so long as the LWF does not
interfere with the control-plane (OID) negotiation of requests involved in
offload, the stack and the NIC driver will happily continue to offload.
This ‘non-interference’ is simply passing through the OIDs opaquely. That
does not sound to this (disclaimer) non-legal person like one would have
implemented any API other than NDIS’ OID Query/Set.
But actually ‘doing’ something in an LWF where some of the stack processing
is offloaded and out of sight of the LWF seems rather limiting in practice.
Cheers,
Dave Cattley
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jan Bottorff
Sent: Wednesday, June 02, 2010 7:21 PM
To: Windows System Software Devs Interest List
Subject: RE: Re:[ntdev] NDIS 5.1 IM filter with a NDIS 6.x NIC on
W2K8/W2K8R2
I know real advice would need to come for real legal people, but any guess
if a NDIS 6.x IM driver with Chimmney pass-thru would require a patent
license from Alacratech? I thought it was the Chimmney API covered by their
patent, and if my IM exposed that API, I might be infringing. Of course the
nic vendor below my IM must have already dealt with the patent issues, so
it’s not clear an IM driver has to deal with a license for an API that must
already be licensed.
Jan
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-413335-
xxxxx@lists.osr.com] On Behalf Of Jeffrey Tippet
Sent: Wednesday, June 02, 2010 3:56 PM
To: Windows System Software Devs Interest List
Subject: RE: Re:[ntdev] NDIS 5.1 IM filter with a NDIS 6.x NIC on
W2K8/W2K8R2You can write a chimney-aware IM driver that will “pass through” the
chimney capability to TCPIP.
http://msdn.microsoft.com/en-us/library/ff570931(v=VS.85).aspxChimney works fine in the presence of LWFs, but the LWFs don’t
participate in the offload. E.g., you can’t intercept and modify
offloaded TCP data streams from a LWF.-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-413256-
xxxxx@lists.osr.com] On Behalf Of Lyndon J. Clarke
Sent: Tuesday, June 01, 2010 3:41 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] NDIS 5.1 IM filter with a NDIS 6.x NIC on
W2K8/W2K8R2Err, maybe I’m not ‘up to date’ here, but I was sure that even NDIS 6.x
LWF basically means than chimney and friends goodness has to be
disabled?wrote in message news:xxxxx@ntdev…
> > I thought of it some more…
> >
> > The problems with ndis51 IM on NDIS6x nic miniports can arise if the
> > underlying NIC supports chimney offload, RSS or VMQ(virtual machine
> > queue). So it really depends on what you plan to do in the IM driver.
> I.E.
> > you won’t be able to see IP, TCP headers for the toe’d streams.
> >
> > If your IM need to interact with those “scalable networking” Windows
> > features, you will need a NDIS6x IM.
> >
> > Good luck,
> > Calvin
> >
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Sorry, just re-read this and see that he (Mr. Tippet) was referring to
Chimney specifically which of course carries with it extra handler support
(to be passed through) in an NDIS6/LWF. I incorrectly let myself think
‘offload’ in general and not Chimney in particular.
Dave Cattley
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of David R. Cattley
Sent: Wednesday, June 02, 2010 7:53 PM
To: Windows System Software Devs Interest List
Subject: RE: Re:[ntdev] NDIS 5.1 IM filter with a NDIS 6.x NIC on
W2K8/W2K8R2
I think what Mr. Tippet is saying is that so long as the LWF does not
interfere with the control-plane (OID) negotiation of requests involved in
offload, the stack and the NIC driver will happily continue to offload.
This ‘non-interference’ is simply passing through the OIDs opaquely. That
does not sound to this (disclaimer) non-legal person like one would have
implemented any API other than NDIS’ OID Query/Set.
But actually ‘doing’ something in an LWF where some of the stack processing
is offloaded and out of sight of the LWF seems rather limiting in practice.
Cheers,
Dave Cattley
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jan Bottorff
Sent: Wednesday, June 02, 2010 7:21 PM
To: Windows System Software Devs Interest List
Subject: RE: Re:[ntdev] NDIS 5.1 IM filter with a NDIS 6.x NIC on
W2K8/W2K8R2
I know real advice would need to come for real legal people, but any guess
if a NDIS 6.x IM driver with Chimmney pass-thru would require a patent
license from Alacratech? I thought it was the Chimmney API covered by their
patent, and if my IM exposed that API, I might be infringing. Of course the
nic vendor below my IM must have already dealt with the patent issues, so
it’s not clear an IM driver has to deal with a license for an API that must
already be licensed.
Jan
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-413335-
xxxxx@lists.osr.com] On Behalf Of Jeffrey Tippet
Sent: Wednesday, June 02, 2010 3:56 PM
To: Windows System Software Devs Interest List
Subject: RE: Re:[ntdev] NDIS 5.1 IM filter with a NDIS 6.x NIC on
W2K8/W2K8R2You can write a chimney-aware IM driver that will “pass through” the
chimney capability to TCPIP.
http://msdn.microsoft.com/en-us/library/ff570931(v=VS.85).aspxChimney works fine in the presence of LWFs, but the LWFs don’t
participate in the offload. E.g., you can’t intercept and modify
offloaded TCP data streams from a LWF.-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-413256-
xxxxx@lists.osr.com] On Behalf Of Lyndon J. Clarke
Sent: Tuesday, June 01, 2010 3:41 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] NDIS 5.1 IM filter with a NDIS 6.x NIC on
W2K8/W2K8R2Err, maybe I’m not ‘up to date’ here, but I was sure that even NDIS 6.x
LWF basically means than chimney and friends goodness has to be
disabled?wrote in message news:xxxxx@ntdev…
> > I thought of it some more…
> >
> > The problems with ndis51 IM on NDIS6x nic miniports can arise if the
> > underlying NIC supports chimney offload, RSS or VMQ(virtual machine
> > queue). So it really depends on what you plan to do in the IM driver.
> I.E.
> > you won’t be able to see IP, TCP headers for the toe’d streams.
> >
> > If your IM need to interact with those “scalable networking” Windows
> > features, you will need a NDIS6x IM.
> >
> > Good luck,
> > Calvin
> >
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Yes, thanks, the legal note is important – you do need a patent license to implement chimney offload on your NIC. However, I do not know if you need a license to implement an IM driver. And even if I did claim an answer to that question, you should not trust me, because I am not a lawyer in your employ.
Incidentally, a LWF does not need (and in fact, has no way to register) extra handlers to pass through chimney. (In contrast, an IM driver does need extra handlers).
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of David R. Cattley
Sent: Wednesday, June 02, 2010 5:13 PM
To: Windows System Software Devs Interest List
Subject: RE: Re:[ntdev] NDIS 5.1 IM filter with a NDIS 6.x NIC on W2K8/W2K8R2
Sorry, just re-read this and see that he (Mr. Tippet) was referring to Chimney specifically which of course carries with it extra handler support
(to be passed through) in an NDIS6/LWF. I incorrectly let myself think
‘offload’ in general and not Chimney in particular.
Dave Cattley
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of David R. Cattley
Sent: Wednesday, June 02, 2010 7:53 PM
To: Windows System Software Devs Interest List
Subject: RE: Re:[ntdev] NDIS 5.1 IM filter with a NDIS 6.x NIC on
W2K8/W2K8R2
I think what Mr. Tippet is saying is that so long as the LWF does not interfere with the control-plane (OID) negotiation of requests involved in offload, the stack and the NIC driver will happily continue to offload.
This ‘non-interference’ is simply passing through the OIDs opaquely. That does not sound to this (disclaimer) non-legal person like one would have implemented any API other than NDIS’ OID Query/Set.
But actually ‘doing’ something in an LWF where some of the stack processing is offloaded and out of sight of the LWF seems rather limiting in practice.
Cheers,
Dave Cattley
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Jan Bottorff
Sent: Wednesday, June 02, 2010 7:21 PM
To: Windows System Software Devs Interest List
Subject: RE: Re:[ntdev] NDIS 5.1 IM filter with a NDIS 6.x NIC on
W2K8/W2K8R2
I know real advice would need to come for real legal people, but any guess if a NDIS 6.x IM driver with Chimmney pass-thru would require a patent license from Alacratech? I thought it was the Chimmney API covered by their patent, and if my IM exposed that API, I might be infringing. Of course the nic vendor below my IM must have already dealt with the patent issues, so it’s not clear an IM driver has to deal with a license for an API that must already be licensed.
Jan
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-413335-
xxxxx@lists.osr.com] On Behalf Of Jeffrey Tippet
Sent: Wednesday, June 02, 2010 3:56 PM
To: Windows System Software Devs Interest List
Subject: RE: Re:[ntdev] NDIS 5.1 IM filter with a NDIS 6.x NIC on
W2K8/W2K8R2You can write a chimney-aware IM driver that will “pass through” the
chimney capability to TCPIP.
http://msdn.microsoft.com/en-us/library/ff570931(v=VS.85).aspxChimney works fine in the presence of LWFs, but the LWFs don’t
participate in the offload. E.g., you can’t intercept and modify
offloaded TCP data streams from a LWF.-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-413256-
xxxxx@lists.osr.com] On Behalf Of Lyndon J. Clarke
Sent: Tuesday, June 01, 2010 3:41 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] NDIS 5.1 IM filter with a NDIS 6.x NIC on
W2K8/W2K8R2Err, maybe I’m not ‘up to date’ here, but I was sure that even NDIS
6.x LWF basically means than chimney and friends goodness has to be
disabled?wrote in message news:xxxxx@ntdev…
> > I thought of it some more…
> >
> > The problems with ndis51 IM on NDIS6x nic miniports can arise if the
> > underlying NIC supports chimney offload, RSS or VMQ(virtual machine
> > queue). So it really depends on what you plan to do in the IM driver.
> I.E.
> > you won’t be able to see IP, TCP headers for the toe’d streams.
> >
> > If your IM need to interact with those “scalable networking” Windows
> > features, you will need a NDIS6x IM.
> >
> > Good luck,
> > Calvin
> >
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
—
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
> Chimney works fine in the presence of LWFs, but the LWFs don’t participate
in the offload. E.g., you can’t intercept and modify offloaded TCP data
streams from a LWF.
Sorry, yeah, that’s exactly what I meant, but you’re right it’s not exactly
what I wrote.