This is a note to let you know that I've just added the patch titled
staging: refresh TODO for rtl8712
to my staging git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
in the staging-linus branch.
The patch will show up in the next release
On 03/22/2016 04:14 PM, kbuild test robot wrote:
Hi Peter,
[auto build test WARNING on wireless-drivers-next/master]
[also build test WARNING on v4.5 next-20160322]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https
From: Colin Ian King
When info->ram_patch is released info->otp_patch is being set
to NULL rather than info->ram_patch. I believe this is a cut-n-paste
bug from almost identical code proceeding it that uses the same
idiom for info->otp_patch.
Signed-off-by: Colin Ian
Hi Peter,
[auto build test WARNING on wireless-drivers-next/master]
[also build test WARNING on v4.5 next-20160322]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Peter-Oh/ath10k-parse-Rx-MAC
Check and parse Rx MAC timestamp when firmware sets its flag
to status variable.
10.4 firmware adds it in Rx beacon frame only at this moment.
Drivers and mac80211 may utilize it to detect such clockdrift
or beacon collision and use the result for beacon collision
avoidance.
Signed-off-by: Peter
'struct timeval' uses a 32-bit seconds field which will overflow in
year 2038 and beyond. This patch is part of a larger effort to remove
all instances of 'struct timeval' from the kernel and replace them
with 64-bit timekeeping variables.
The correctness of the code isn't affected by this patch -
On 22-3-2016 7:36, Rafał Miłecki wrote:
> On 3 March 2016 at 23:37, Rafał Miłecki wrote:
>> brcmfmac in general is not capable of removing interfaces. If you take
>> a look at brcmf_cfg80211_del_iface implementation, you'll see it
>> returns -EOPNOTSUPP (except for p2p
On Tue, 2016-03-22 at 12:23 +0530, Ashwini Singh wrote:
> Signed-off-by: Ashwini Singh
It might be better to break this into a few different patches.
o Remove trailing whitespace
o Fix vertical line / brace location
o Multi-line statement parenthesis alignment
o Space
We have a huge cc list on this thread, and admittedly this work does
cut across a great deal of wireless, potentially, but does netdev need
to be on it?
there's been nothing codel specific on it in a while, so I cut those
from the cc.
On Tue, Mar 22, 2016 at 1:05 AM, Michal Kazior
On Tue, Mar 22, 2016 at 3:05 AM, Reinoud Koornstra
wrote:
> Thanks, that answers my question.
Adding this to /etc/sysctl.conf or /etc/sysctl.d/bufferbloat.conf is
generally what we do
net.core.default_qdisc=fq_codel
A lot of us are running ecn by default and put in
Since tx completion and rx indication processing are moved out
of txrx tasklet and rx ring lock contention also removed from txrx
for rx_ind messages, it would be efficient to combine both replenish
and txrx tasks. Refill threshold is adjusted for both AP135 and AP148
(low and high end systems).
Whenever htt rx indication i.e target to host messages are received
on rx copy engine (CE5), the message will be freed after processing
the response. Then CE 5 will be refilled with new descriptors at
post rx processing. This memory alloc and free operations can be avoided
by reusing the same
The physical address necessary to unmap DMA ('bufferp') is stored
in ath10k_skb_cb as 'paddr'. For diag register read and write
operations, 'paddr' is stored in transfer context. ath10k doesn't rely
on the meta/transfer_id. So the unused output arguments {bufferp, nbytesp
and transfer_idp} are
Except qca61x4 family chips (qca6164, qca6174), copy engine 5 is used
for receiving target to host htt messages. In follow up patch, CE5
descriptors will be reused. In such case, same API can not be used as
htc layer callback where the response messages will be freed at the end.
Hence register new
In follow up patch, htt rx descriptors will be reused instead of
dealloc and refill. To achieve that htt rx indication messages
should not be deferred and should be processed in pci tasklet itself.
Also from rx indication message, mpdu_count alone is used. So it is
maintained as atomic variable
Make amsdu handlers (i.e amsdu_pop and rx_h_handler) common to both
rx_ind and frag_ind htt events. It is sufficient to hold rx_ring lock
for amsdu_pop alone and no need to hold it until the packets are
delivered to mac80211. This helps to reduce rx_lock contention as well.
Signed-off-by:
The fw descriptor was never used and probably never will be. It makes
little sense to maintain support for it. Remove it and simplify rx
processing. This will make it easier to optimize rx processing later
as well.
Signed-off-by: Rajkumar Manoharan
---
To optmize CPU usage htt rx descriptors will be reused instead of
refilling it for htt rx copy engine (CE5). To support that all htt rx
indications should be proecssed at same context. Instead of queueing
actual indication message, queue copied message for txrx processing.
Signed-off-by: Rajkumar
To optimize CPU usage htt rx descriptors will be reused instead of
refilling it for htt rx copy engine (CE5). To support that all htt rx
indications should be processed at same context. FIFO queue is used
to maintain tx completion status for each msdu. This helps to retain
the order of tx
Hi All,
In order to reuse HTT Rx descriptor (copy engine 5), HTT response
processing should be decoupled from txrx data processing. This change also
helps to reduce rx ring lock contention. As txrx tasklet's work load is
reduced, rx replenish task can be combined with txrx_task. Refilling
On Tuesday 22 March 2016 02:55:22 Tina Ruchandani wrote:
> Truly fixing this would
> require changing the debug print to print more than 8 digits and using
> a different specifier from %li.
Why not just change it to %lli, and a cast to s64? I don't think the
format string or the number of
Thanks, that answers my question.
Ok, so currently Cake didn't make it into the 4.4 kernel yet I noticed.
Are there plans to add this or are there still many issues to be worked out?
In the mean time I followed some instructions to build the module and
iproute2 for cake.
sudo tc qdisc add dev
'struct timeval' uses a 32-bit seconds field which will overflow in
year 2038 and beyond. This patch is part of a larger effort to remove
all instances of 'struct timeval' from the kernel and replace them
with 64-bit timekeeping variables.
The correctness of the code isn't affected by this patch -
Michal Kazior writes:
> traffic-gen generates only BE traffic. Everything else runs UDP_RR
> which doesn't generate a lot of traffic.
Good point. Fixed that: the newest git version of traffic-gen supports a
-t parameter which will be set as the TOS byte on outgoing
On 22/03/16 10:37, Reinoud Koornstra wrote:
Hi Everyone,
Everytime I boot I need to set fq_codel for my wireless interface:
sudo tc qdisc add dev wlp4s0 root fq_codel
I also need to sudo sysctl -w net.core.default_qdisc=fq_codel
Is there a good way to have this as the default in the kernel
Hi Everyone,
Everytime I boot I need to set fq_codel for my wireless interface:
sudo tc qdisc add dev wlp4s0 root fq_codel
I also need to sudo sysctl -w net.core.default_qdisc=fq_codel
Is there a good way to have this as the default in the kernel config
instead of pfifo?
Also, are there
On 21 March 2016 at 18:10, Dave Taht wrote:
> thx.
>
> a lot to digest.
>
> A) quick notes on "flent-gui bursts_11e-2016-03-21T09*.gz"
>
> 1) the new bursts_11e test *should* have stuck stuff in the VI and VO
> queues, and there *should* have been some sort of difference
Signed-off-by: Ashwini Singh
---
drivers/net/wireless/ath/ath9k/ani.c|2 +-
drivers/net/wireless/ath/ath9k/antenna.c|2 +-
drivers/net/wireless/ath/ath9k/ar9002_hw.c |2 +-
drivers/net/wireless/ath/ath9k/ar9002_phy.c |2 +-
On 22 March 2016 at 02:35, David Lang wrote:
> On Wed, 16 Mar 2016, Michal Kazior wrote:
>
>> Since 11n aggregation become important to get the
>> best out of txops. However aggregation inherently
>> requires buffering and queuing. Once variable
>> medium conditions to different
On 3 March 2016 at 23:37, Rafał Miłecki wrote:
> brcmfmac in general is not capable of removing interfaces. If you take
> a look at brcmf_cfg80211_del_iface implementation, you'll see it
> returns -EOPNOTSUPP (except for p2p interfaces).
>
> However there is problem in handling
30 matches
Mail list logo