Re: [PATCH 1/3] mmc: sdio: Add API to manage SDIO IRQs from a workqueue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ulf

On Thu, Apr 20, 2017 at 5:14 AM, Ulf Hansson <ulf.hansson@xxxxxxxxxx> wrote:
> [...]
>
>>
>> With "cap-sdio-irq" commented out but without your 3 patches:
>> => Boot up, "ifconfig eth0 down; ping -c 20 8.8.8.8".  Seems OK.
>>
>> With "cap-sdio-irq" commented out but _with_ your 3 patches:
>> => Boot up, "ifconfig eth0 down; ping -c 20 8.8.8.8".  Seems OK.
>>
>> So I guess the conclusion is that I missed the part about your patch
>> only enabling the new features if MMC_CAP_SDIO_IRQ.  Sorry.  :(
>> ...and then I must have hit some other unrelated failure that I can't
>> reproduce now and assumed it was your patch's fault.
>>
>> So basically I would say that I've lightly tested your code.  It's not
>> code I've stressed a ton, but it survived some basic tests anyway...
>> :)  The code also looks pretty sane to me.
>
> Thanks a lot for your feedback a for running a new round of tests.
> This seems promising then!
>
> When you have the time, it we awesome if you could run yet another new
> round of test with the new version of the series. I posted it
> yesterday evening my local time.

Sorry for taking so long to get to this.  I've done this now and
things seem to be working fine with your new series.  As with before,
I'm not doing really stressful testing here, but what I've done seems
OK.


> I would also be very interested to know if converting to the work
> queue approach has any impact on throughput. Maybe you have some
> simple test suite to also verify that?

I don't personally.  To really get something repeatable for WiFi, you
need things in a chamber and need a test server setup.

I did this quick test with the device sitting on my desk (with
whatever the closest WiFi access point was), though:

ifconfig eth0 down
for i in $(seq 5); do
  curl http://SomeBigFile > /dev/null
done


>From this very simple test, the performance looks like a wash.

--

Before your changes:

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 54.0M  100 54.0M    0     0  2753k      0  0:00:20  0:00:20 --:--:-- 2952k
100 54.0M  100 54.0M    0     0  1073k      0  0:00:51  0:00:51 --:--:--  902k
100 54.0M  100 54.0M    0     0  2494k      0  0:00:22  0:00:22 --:--:-- 3061k
100 54.0M  100 54.0M    0     0  2455k      0  0:00:22  0:00:22 --:--:-- 2890k
100 54.0M  100 54.0M    0     0  1934k      0  0:00:28  0:00:28 --:--:-- 2301k

After your changes:

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 54.0M  100 54.0M    0     0  2376k      0  0:00:23  0:00:23 --:--:-- 2739k
100 54.0M  100 54.0M    0     0  2303k      0  0:00:24  0:00:24 --:--:-- 2698k
100 54.0M  100 54.0M    0     0  2512k      0  0:00:22  0:00:22 --:--:-- 2359k
100 54.0M  100 54.0M    0     0  1774k      0  0:00:31  0:00:31 --:--:-- 1742k
100 54.0M  100 54.0M    0     0  2124k      0  0:00:26  0:00:26 --:--:-- 2753k

--

It's possible that Brian Norris (CCed) might have an easy way to do a
better test?

-Doug
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux USB Devel]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux