linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Dongas <dongas86@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org
Subject: Re: Throughput is not changed when setting to a much higher bit rate
Date: Thu, 21 May 2009 18:38:20 -0400	[thread overview]
Message-ID: <1242945500.6444.24.camel@localhost.localdomain> (raw)
In-Reply-To: <60ce8d250905201700v13fe1394l6a9704bb02be3807@mail.gmail.com>

On Thu, 2009-05-21 at 08:00 +0800, Dongas wrote:
> 2009/5/21 Dan Williams <dcbw@redhat.com>:
> > On Wed, 2009-05-20 at 22:48 +0800, Dongas wrote:
> >> 2009/5/20 John W. Linville <linville@tuxdriver.com>:
> >> > On Wed, May 20, 2009 at 01:48:32AM +0800, Dongas wrote:
> >> >
> >> >> Why the bandwidth is not changed when bit rate is changed to 11Mb/s?
> >> >> Any thing wrong?
> >> >
> >> > More errors at higher bit rate, resulting in more retries?  Just a
> >> > thought...
> >> >
> >> Is there a quick way to verify this possible reason? I'm using Libertas driver.
> >>
> >> BTW, my sdio host driver is using polling mode to handle SDIO IRQ.
> >> Could this be the cause of such poor performance?
> >
> > Definitely.  With libertas, the largest class of issues by *far* that
> > we've seen are controller related.  I seem to recall that I've pulled
> > about 6Mbps through the card using a normal Ricoh controller from a
> > Fujitsu laptop.  I can recheck that.
> 
> AFAIK, most old laptop ,including my x61, doesn't support SDIO in HW.
> So did Ricoh controller you tested use polling mode to handle SDIO IRQ?
> Which clock of controller and which bit rate did you test?

Actually, most of the older machines *can* do SDIO, those made from
about 2006 - 2009.  These days a lot of the SD "controllers" are
actually USB-based mass-storage converters and cannot do SDIO, they are
essentially 10-in-1 cardreaders.

What is the 'lspci' output for your Thinkpad?  If the controller isn't
in 'lspci' but is in 'lsusb', then it's quite unlikely to work because
of the above reason, I think.

Dan

> >> (However I just can't believe the performance is so poor ,only around
> >> 1.1Mbps, with polling mode of SDIO IRQ)
> >
> > What specific kernel version are you using?  There have been some
> > latency fixes in recent kernels, but would be good to know just to make
> > sure.
> 
> I'm using kenrel 2.6.25.
> 
> Thanks
> 
> Regards
> Dongas


  parent reply	other threads:[~2009-05-21 22:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19 17:48 Throughput is not changed when setting to a much higher bit rate Dongas
2009-05-19 17:53 ` John W. Linville
2009-05-20 14:48   ` Dongas
2009-05-20 21:23     ` Dan Williams
2009-05-21  0:00       ` Dongas
2009-05-21 17:37         ` Andrey Yurovsky
2009-05-21 22:38         ` Dan Williams [this message]
2009-05-21 23:11           ` Andrey Yurovsky
     [not found]             ` <200905212349.n4LNnxQH029607@ms.infomax.com.tw>
2009-05-21 23:53               ` Andrey Yurovsky
2009-05-22  0:00                 ` Dongas
2009-05-22  0:27       ` Dongas
2009-05-22  3:49         ` Dan Williams
2009-05-22 16:37           ` Dongas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1242945500.6444.24.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=dongas86@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).