linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernhard Schiffner <bernhard@schiffner-limbach.de>
To: andrea.merello@gmail.com
Cc: ralf@czekalla.com, Xose Vazquez Perez <xose.vazquez@gmail.com>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>
Subject: Re: Rtl8187se regression [was: rtl8187se - serious regressions since merge out of staging into 818x]
Date: Fri, 12 Sep 2014 09:47:38 +0200	[thread overview]
Message-ID: <1472277.xX1dghvxoC@bs8> (raw)
In-Reply-To: <CAN8YU5NOApnft04+N3rSQF3j9d9N47-A6m4n-1-2KNHq+1EYKA@mail.gmail.com>

Hi Anrea, Larry,

I used the new driver (still without the latest patches) only in hotels slow 
DSL/Wireless environment and there I noted no regression.

Because of the problems I'am going now to a special site, where I have a local 
networks (LAN/WLAN), good internet connection and root access to Linux 
machines.
This should be a good thing to do real testing.

1.) Andrea, can you resend me the latest patches (perhaps against 3.16) 
please?
(only to confirm that we are in "synchronous" mode.)

2.) Andrea, Larry, John are you interested to have root access to my laptop 
using the rtl8187se?
(Perhaps it can stay there over the weekend too.)

3.) My test for maximal troughput is to run a connection /dev/zero -> nc ->|-> 
nc -> /dev/null.
Any other ideas?

4.) I think to have this setup ready about 11:30 UTC.

I'am open to any suggestion from your side.


Bernhard

Am Freitag, 12. September 2014, 02:18:03 schrieb Andrea Merello:
> My aplogies for this quick and a bit messy reply: I m from mobile.
> 
> @Xose
> Thank you for forwarding me that. I wasn t aware of it.
> 
> (BTW a couple of other people reported a similar issue)
> 
> @Ralf
> The driver still have some not implemented features, including signal
> strenght measure, furthermore some fixes that might improve performances
> should be on the way for 3.17.
> 
> @Larry, Bernhard
> I think those fixes was basically the same of some RFT patch I sent you
> some time ago..
> Have you had any occasion to test those patches?
> 
> @Ralf, all..
> I must say that I never been able to reproduce any severe performance
> regression here, for this reason I'm asking people who reports this to make
> some testing for me if possible..
> 
> Here you can find  a similar report and my answer where I asked for the
> tests:
> https://bugzilla.kernel.org/show_bug.cgi?id=83631
> 
> If you could do some of those test for me, that would be great.
> 


       reply	other threads:[~2014-09-12  7:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAN8YU5NOApnft04+N3rSQF3j9d9N47-A6m4n-1-2KNHq+1EYKA@mail.gmail.com>
2014-09-12  7:47 ` Bernhard Schiffner [this message]
2014-09-12 16:29   ` Rtl8187se regression [was: rtl8187se - serious regressions since merge out of staging into 818x] Andrea Merello
2014-09-12 16:52     ` Larry Finger

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=1472277.xX1dghvxoC@bs8 \
    --to=bernhard@schiffner-limbach.de \
    --cc=Larry.Finger@lwfinger.net \
    --cc=andrea.merello@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=ralf@czekalla.com \
    --cc=xose.vazquez@gmail.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).