All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: linux-wireless@vger.kernel.org,
	James Hughes <james.hughes@raspberrypi.org>
Subject: Re: [PATCH 3/4] brcmfmac: rework headroom check in .start_xmit()
Date: Wed, 28 Jun 2017 00:07:10 +0200	[thread overview]
Message-ID: <0d8f0be4-4487-5f0d-c903-c87656c96bac@broadcom.com> (raw)
In-Reply-To: <874lv15xp9.fsf@purkki.adurom.net>

On 27-06-17 16:09, Kalle Valo wrote:
> Arend van Spriel <arend.vanspriel@broadcom.com> writes:
> 
>> Since commit 9cc4b7cb86cb ("brcmfmac: Make skb header writable
>> before use") the headroom usage has been fixed. However, the
>> driver was keeping statistics that got lost. So reworking the
>> code so we get those driver statistics back for debugging.
>>
>> Cc: James Hughes <james.hughes@raspberrypi.org>
>> Reviewed-by: Hante Meuleman <hante.meuleman@broadcom.com>
>> Reviewed-by: Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>
>> Reviewed-by: Franky Lin <franky.lin@broadcom.com>
>> Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
>> ---
>>  .../net/wireless/broadcom/brcm80211/brcmfmac/bus.h | 15 ++++++++++++--
>>  .../wireless/broadcom/brcm80211/brcmfmac/core.c    | 23 +++++++++++++++-------
>>  .../wireless/broadcom/brcm80211/brcmfmac/sdio.c    | 13 +++++++-----
>>  3 files changed, 37 insertions(+), 14 deletions(-)
>>
>> diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bus.h b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bus.h
>> index e1a4d9e..163ddc4 100644
>> --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bus.h
>> +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bus.h
>> @@ -113,6 +113,17 @@ struct brcmf_bus_msgbuf {
>>  
>>  
>>  /**
>> + * struct brcmf_bus_stats - bus statistic counters.
>> + *
>> + * @pktcowed: packets cowed for extra headroom/unorphan.
>> + * @pktcow_failed: packets dropped due to failed cow-ing.
>> + */
>> +struct brcmf_bus_stats {
>> +	atomic_t pktcowed;
>> +	atomic_t pktcow_failed;
>> +};
> 
> Same question as in the previous patch. I only see updates for these
> variables, but nobody reading them?

Hi Kalle,

You are right. My intention was to expose these to debugfs, but clearly
did not include it in this patch series. So how do you want to handle
this. Feel free to drop patch 2 and 3. I can resubmit them with
subsequent patches dealing with exposing it to debugfs if that makes
more sense.

Regards,
Arend

  reply	other threads:[~2017-06-27 22:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-22 10:01 [PATCH 0/4] brcm80211: general admin and headroom rework Arend van Spriel
2017-06-22 10:01 ` [PATCH 1/4] brcmfmac: cleanup kerneldoc for struct brcmf_bus Arend van Spriel
2017-06-28 17:53   ` [1/4] " Kalle Valo
2017-06-22 10:01 ` [PATCH 2/4] brcmfmac: use atomic_t for statistic counter in " Arend van Spriel
2017-06-27 14:05   ` Kalle Valo
2017-06-22 10:01 ` [PATCH 3/4] brcmfmac: rework headroom check in .start_xmit() Arend van Spriel
2017-06-27 14:09   ` Kalle Valo
2017-06-27 22:07     ` Arend van Spriel [this message]
2017-06-28 16:04       ` Kalle Valo
2017-06-22 10:01 ` [PATCH 4/4] MAINTAINERS: add brcm80211 maintainer info from Cypress Arend van Spriel

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=0d8f0be4-4487-5f0d-c903-c87656c96bac@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=james.hughes@raspberrypi.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.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.