Re: NDIS - asymmetric link speed

From: Arkady Frenkel (arkadyf_at_hotmailxdotxcom)
Date: 01/14/05 

Date: Fri, 14 Jan 2005 13:58:24 +0200

Pavel !
Be aware that speed changed due to duplex mode set from/in registry too
Arkady

"Pavel A." <pavel_a@NOwritemeNO.com> wrote in message
news:eq1tQre#EHA.3708@TK2MSFTNGP14.phx.gbl...
> Dear NDIS gurus,
> Now I have adapter with asymmetric send/receive speed ( uplink speed about
1/3... 1/4 of downlink).
> The media type is ethernet (generic or, possibly, 802.11 emulated).
> How TCPIP relies on link speed value reported by driver? which link speed
the driver should report?
> And same question, if the device does throttling and prioritizing - the
actual link speed
> is different for different payload types.
>
> The marketing, sure enough, wants to display the biggest speed value...
>
> Thanks,
> Pavel
>
>
>
>

Relevant Pages

  • Re: SCSI tape [more info]
    ... > I tried that on the 29160 adapter. ... > Is it time to file a bug report? ... This is sounding a lot like a problem I ran into with a DDS-2 tape ... This was using an Adaptec 2940 SCSI adapter and the aic7xxx driver. ...
    (Fedora)
  • Re: SCSI tape [more info]
    ... >> I tried that on the 29160 adapter. ... >> Is it time to file a bug report? ... >I'm reasonably sure that neither the SCSI adapter nor the driver was ... the same adapter and driver work just fine on a DDS-3 tape ...
    (Fedora)
  • Re: [PATCH 6/6] RTC: Trivially probe for an M41T80 (#2)
    ... driver to not attach to the device if it is in fact not there sounds ... Some do report they probe though. ... the SWARM can either have a ST M41T81 or a Xicor X1241 RTC. ... done at the time the card, including the adapter, is initialized. ...
    (Linux-Kernel)
  • Re: NDIS - asymmetric link speed
    ... >> How TCPIP relies on link speed value reported by driver? ... > the driver should report? ... >> is different for different payload types. ...
    (microsoft.public.development.device.drivers)
  • Re: Blue screen on surprise removal
    ... i exactly i dont know wher the problem is and this is the first ... Pavel A. wrote: ... you've catched a bug in your driver. ... I run the windbg tool,Kernel debugger,to the symbol file path i had ...
    (microsoft.public.development.device.drivers)