Hi all,
I use XP x86 and want to report to the os 20 Gbps for the network adapter. The os shows only 2Gbps. Spending time around psched!PsUpdateLinkSpeed, I see no protection on overflows. Has anyone done it?
Regards,
Calin
Unbind PSCHED from your adapter if you are worried about PSCHED. Then you can at least verify that your Miniport is actually reporting the speed correctly and/or that the system accepts the value you are reporting. If putting PSCHED back causes the speed reported to go from 20Gbps to 2Gbps then file a bug with MSFT.
Good Luck,
Dave Cattley
Date: Wed, 12 May 2010 08:00:07 -0700
From: xxxxx@yahoo.com
Subject: [ntdev] ndis link speed
To: xxxxx@lists.osr.comHi all,
I use XP x86 and want to report to the os 20 Gbps for the network adapter. The os shows only 2Gbps. Spending time around psched!PsUpdateLinkSpeed, I see no protection on overflows. Has anyone done it?
Regards,
Calin
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminarsTo unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
This is a known issue with Windows XP, and I don’t think you can work around it merely by unbinding PSCHED. NDIS 6 natively supports 64-bit link speeds et al, while prior versions of NDIS do not. See http://support.microsoft.com/kb/931857 .
Also see RFC 2863:
ifSpeed OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
“An estimate of the interface’s current bandwidth in bits
per second. For interfaces which do not vary in bandwidth
or for those where no accurate estimation can be made, this
object should contain the nominal bandwidth. If the
bandwidth of the interface is greater than the maximum value
reportable by this object then this object should report its
maximum value (4,294,967,295) and ifHighSpeed must be used
to report the interace’s speed. For a sub-layer which has
no concept of bandwidth, this object should be zero.”
::= { ifEntry 5 }
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of David Cattley
Sent: Wednesday, May 12, 2010 8:57 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] ndis link speed
Unbind PSCHED from your adapter if you are worried about PSCHED. Then you can at least verify that your Miniport is actually reporting the speed correctly and/or that the system accepts the value you are reporting. If putting PSCHED back causes the speed reported to go from 20Gbps to 2Gbps then file a bug with MSFT.
Good Luck,
Dave Cattley
Date: Wed, 12 May 2010 08:00:07 -0700
From: xxxxx@yahoo.commailto:xxxxx
> Subject: [ntdev] ndis link speed
> To: xxxxx@lists.osr.commailto:xxxxx
>
> Hi all,
>
> I use XP x86 and want to report to the os 20 Gbps for the network adapter. The os shows only 2Gbps. Spending time around psched!PsUpdateLinkSpeed, I see no protection on overflows. Has anyone done it?
>
> Regards,
> Calin
>
>
>
>
> —
> 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</mailto:xxxxx></mailto:xxxxx>
Hi,
I would add that XP x64 does show 20 Gbps on the same driver. I only compiled it for x64, with the size of the OID_GEN_LINK_SPEED request being 4, same as for x86.
Regards, Calin
— On Wed, 5/12/10, Jeffrey Tippet wrote:
From: Jeffrey Tippet
Subject: RE: [ntdev] ndis link speed
To: “Windows System Software Devs Interest List”
Date: Wednesday, May 12, 2010, 9:39 PM
This is a known issue with Windows XP, and I don’t think you can work around it merely by unbinding PSCHED. NDIS 6 natively supports 64-bit link speeds et al, while prior versions of NDIS do not. See http://support.microsoft.com/kb/931857 . Also see RFC 2863: ifSpeed OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION “An estimate of the interface’s current bandwidth in bits per second. For interfaces which do not vary in bandwidth or for those where no accurate estimation can be made, this object should contain the nominal bandwidth. If the bandwidth of the interface is greater than the maximum value reportable by this object then this object should report its maximum value (4,294,967,295) and ifHighSpeed must be
used to report the interace’s speed. For a sub-layer which has no concept of bandwidth, this object should be zero.” ::= { ifEntry 5 } From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of David Cattley
Sent: Wednesday, May 12, 2010 8:57 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] ndis link speed Unbind PSCHED from your adapter if you are worried about PSCHED. Then you can at least verify that your Miniport is actually reporting the speed correctly and/or that the system accepts the value you are reporting. If putting PSCHED back causes the speed reported to go from 20Gbps to 2Gbps then file a bug with MSFT.
Good Luck,
Dave Cattley
> Date: Wed, 12 May 2010 08:00:07 -0700
> From: xxxxx@yahoo.com
> Subject: [ntdev] ndis link speed
> To: xxxxx@lists.osr.com
>
> Hi all,
>
> I use XP x86 and want to report to the os 20 Gbps for the network adapter. The os shows only 2Gbps. Spending time around psched!PsUpdateLinkSpeed, I see no protection on overflows. Has anyone done it?
>
> Regards,
> Calin
>
>
>
>
> —
> 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
Calin Iaru wrote:
I would add that XP x64 does show 20 Gbps on the same driver. I only
compiled it for x64, with the size of the OID_GEN_LINK_SPEED request
being 4, same as for x86.
That’s because XP 64 is not really XP. It’s Windows Server 2003, but
someone used a text editor to replace all publicly visible occurrences
of the string “Server 2003” with XP. The kernel is WS2003, which
doesn’t have this limitation.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Hi Jeffrey,
I report -1 for OID_GEN_LINK_SPEED to indicate to the OS that there’s more and consequently shows the maximum 4Gbps. Thanks for taking the time to answer this question. It would have been much harder for me to locate the explanation within the aforementioned RFC.
Regards,
Calin
From: Jeffrey Tippet
To: Windows System Software Devs Interest List
Sent: Wed, May 12, 2010 8:39:02 PM
Subject: RE: [ntdev] ndis link speed
This is a known issue with Windows XP, and I don’t think you can work around it merely by unbinding PSCHED. NDIS 6 natively supports 64-bit link speeds et al, while prior versions of NDIS do not. See http://support.microsoft.com/kb/931857 .
Also see RFC 2863:
ifSpeed OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
“An estimate of the interface’s current bandwidth in bits
per second. For interfaces which do not vary in bandwidth
or for those where no accurate estimation can be made, this
object should contain the nominal bandwidth. If the
bandwidth of the interface is greater than the maximum value
reportable by this object then this object should report its
maximum value (4,294,967,295) and ifHighSpeed must be used
to report the interace’s speed. For a sub-layer which has
no concept of bandwidth, this object should be zero.”
::= { ifEntry 5 }
From:xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of David Cattley
Sent: Wednesday, May 12, 2010 8:57 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] ndis link speed
Unbind PSCHED from your adapter if you are worried about PSCHED. Then you can at least verify that your Miniport is actually reporting the speed correctly and/or that the system accepts the value you are reporting. If putting PSCHED back causes the speed reported to go from 20Gbps to 2Gbps then file a bug with MSFT.
Good Luck,
Dave Cattley
> Date: Wed, 12 May 2010 08:00:07 -0700
> From: xxxxx@yahoo.com
> Subject: [ntdev] ndis link speed
> To: xxxxx@lists.osr.com
>
> Hi all,
>
> I use XP x86 and want to report to the os 20 Gbps for the network adapter. The os shows only 2Gbps. Spending time around psched!PsUpdateLinkSpeed, I see no protection on overflows. Has anyone done it?
>
> Regards,
> Calin
>
>
>
>
> —
> 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