All of lore.kernel.org
 help / color / mirror / Atom feed
From: Evgeniy Dushistov <dushistov@mail.ru>
To: b43-dev@lists.infradead.org
Subject: slow connection
Date: Sat, 1 Nov 2014 01:41:24 +0300	[thread overview]
Message-ID: <20141031224124.GA9697@fifteen> (raw)
In-Reply-To: <CACna6rw8JdXqikBp=VpALDR-xKGAgf32x5W7ktr2Cj1L+dgePw@mail.gmail.com>

On Fri, Oct 31, 2014 at 09:12:39PM +0100, Rafa? Mi?ecki wrote:
> > So it is 3.18 Mbit/s vs 71.57 MBit/s under the same conditions,
> > and the only difference is OS.
> >
> > Any hints, how to speedup connection under linux?
> 
> We have some improvements for HT-PHY (BCM4331) in 3.18-rc1 (and
> newer). Could you try it?
> 
> b43 is still limited to 802.11g speeds, but I hope it will be better
> than 3.18 Mb/s.
> 

I got:
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 2147M  100 2147M    0     0  2246k      0  0:16:18  0:16:18 --:--:-- 1842k

real    16m18.774s
user    0m27.340s
sys     0m36.350s

This is ~ 17.55Mbit/s for file transfer.
What is much, much better. Thank you.

Are these changes(3.16 [slow b43] vs 3.18 [fast b43]) located 
in drivers/net/wireless/b43?
I would like to port them(changes) to my 3.16 kernel.

By the way, during test connection was hang,
and I can not ping any machine outside of my notebook.

I rmmod/modprobe b43, restart wpa_supplicant/dhcpcd
and all back to normal. 
And after restart I was unable to reproduce it(bug).
dmesg also show nothing. Any hints how to debug such
kind of issues, if I see it again?


-- 
/Evgeniy

  reply	other threads:[~2014-10-31 22:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31 19:00 slow connection Evgeniy Dushistov
2014-10-31 20:12 ` Rafał Miłecki
2014-10-31 22:41   ` Evgeniy Dushistov [this message]
2014-10-31 23:15     ` Rafał Miłecki

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=20141031224124.GA9697@fifteen \
    --to=dushistov@mail.ru \
    --cc=b43-dev@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.