Am 31.01.2018 um 14:46 schrieb Toke Høiland-Jørgensen:
Sebastian Gottschall writes:
Am 31.01.2018 um 12:50 schrieb Toke Høiland-Jørgensen:
Sebastian Gottschall writes:
Am 30.01.2018 um 19:55 schrieb Toke Høiland-Jørgensen:
Ben Greear
Sebastian Gottschall writes:
> Am 31.01.2018 um 12:50 schrieb Toke Høiland-Jørgensen:
>> Sebastian Gottschall writes:
>>
>>> Am 30.01.2018 um 19:55 schrieb Toke Høiland-Jørgensen:
Ben Greear writes:
>> I'm
Am 31.01.2018 um 12:50 schrieb Toke Høiland-Jørgensen:
Sebastian Gottschall writes:
Am 30.01.2018 um 19:55 schrieb Toke Høiland-Jørgensen:
Ben Greear writes:
I'm actually working on reworking that whole scheduler logic, and move
some of it
Sebastian Gottschall writes:
> Am 30.01.2018 um 19:55 schrieb Toke Høiland-Jørgensen:
>> Ben Greear writes:
>>
I'm actually working on reworking that whole scheduler logic, and move
some of it into mac80211. Could you test this (WiP)
Am 30.01.2018 um 19:55 schrieb Toke Høiland-Jørgensen:
Ben Greear writes:
I'm actually working on reworking that whole scheduler logic, and move
some of it into mac80211. Could you test this (WiP) patch and see if
that has the same problem?
It had some serious
Ben Greear writes:
>> I'm actually working on reworking that whole scheduler logic, and move
>> some of it into mac80211. Could you test this (WiP) patch and see if
>> that has the same problem?
>
> It had some serious conflicts in ath10k, due to my local changes, so
> I
On 01/30/2018 04:07 AM, Toke Høiland-Jørgensen wrote:
Ben Greear writes:
Maybe there is some way for the scheduler to get stuck and not
schedule anything?
It would appear so, yeah. Do you do anything special other than
associate a whole bunch of stations to trigger
Ben Greear writes:
> Maybe there is some way for the scheduler to get stuck and not
> schedule anything?
It would appear so, yeah. Do you do anything special other than
associate a whole bunch of stations to trigger this? I can try to see if
I can script something that
On 01/29/2018 02:35 PM, Toke Høiland-Jørgensen wrote:
Ben Greear writes:
On 01/29/2018 01:47 PM, Toke Høiland-Jørgensen wrote:
Ben Greear writes:
On 01/27/2018 05:11 AM, Toke Høiland-Jørgensen wrote:
Ben Greear
Ben Greear writes:
> On 01/29/2018 01:47 PM, Toke Høiland-Jørgensen wrote:
>> Ben Greear writes:
>>
>>> On 01/27/2018 05:11 AM, Toke Høiland-Jørgensen wrote:
Ben Greear writes:
> I'm doing a test with 200
On 01/29/2018 01:47 PM, Toke Høiland-Jørgensen wrote:
Ben Greear writes:
On 01/27/2018 05:11 AM, Toke Høiland-Jørgensen wrote:
Ben Greear writes:
I'm doing a test with 200 virtual stations on each of 6 ath9k radios.
When I configure
Ben Greear writes:
> On 01/27/2018 05:11 AM, Toke Høiland-Jørgensen wrote:
>> Ben Greear writes:
>>
>>> I'm doing a test with 200 virtual stations on each of 6 ath9k radios.
>>>
>>> When I configure stations for DHCP, I see cases where stations
On 01/27/2018 05:11 AM, Toke Høiland-Jørgensen wrote:
Ben Greear writes:
I'm doing a test with 200 virtual stations on each of 6 ath9k radios.
When I configure stations for DHCP, I see cases where stations on a particular
radio will not transmit anything sometimes.
Ben Greear writes:
> I'm doing a test with 200 virtual stations on each of 6 ath9k radios.
>
> When I configure stations for DHCP, I see cases where stations on a particular
> radio will not transmit anything sometimes. I see no 'XMIT' logs that show
> indication of
>
I'm doing a test with 200 virtual stations on each of 6 ath9k radios.
When I configure stations for DHCP, I see cases where stations on a particular
radio will not transmit anything sometimes. I see no 'XMIT' logs that show
indication of
frames being received in the driver from the upper
15 matches
Mail list logo