linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 3/4] ath10k: implement 802.3 SNAP rx decap type A-MSDU handling
Date: Mon, 12 Aug 2013 17:55:42 +0300	[thread overview]
Message-ID: <878v07t0up.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1375949813-10969-4-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Thu, 8 Aug 2013 10:16:52 +0200")

Michal Kazior <michal.kazior@tieto.com> writes:

> This enables driver to rx another decapped a-msdu
> frames. It should possibly help with throughputs
> in some cases and reduce (or eliminate) number of
> messages like this:
>
>   ath10k: error processing msdus -524
>
> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>

[...]

> @@ -659,6 +658,15 @@ static int ath10k_htt_rx_amsdu(struct ath10k_htt *htt,
>  			decap_hdr += roundup(crypto_len, 4);
>  		}
>  
> +		if (fmt == RX_MSDU_DECAP_8023_SNAP_LLC) {
> +			/* SNAP 802.3 consists of:
> +			 * [dst:6][src:6][len:2][dsap:1][ssap:1][ctl:1][snap:5]
> +			 * [data][fcs:4].
> +			 *
> +			 * Since this overlaps with A-MSDU header (da, sa, len)
> +			 * there's nothing extra to do. */
> +		}

This block doesn't have any code, is that on purpose? Most likely a
static checker finds this later and we need to remove it.

If your idea is to document the LLC case (which is very good!) it's
better to do everything inside a comment, for example like this:

	/* When fmt == RX_MSDU_DECAP_8023_SNAP_LLC:
         *
         * SNAP 802.3 consists of:
	 * [dst:6][src:6][len:2][dsap:1][ssap:1][ctl:1][snap:5]
	 * [data][fcs:4].
	 *
	 * Since this overlaps with A-MSDU header (da, sa, len)
	 * there's nothing extra to do. */

-- 
Kalle Valo

  reply	other threads:[~2013-08-12 14:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-08  8:16 [PATCH 0/4] ath10k: fixes Michal Kazior
2013-08-08  8:16 ` [PATCH 1/4] ath10k: fix HTT service setup Michal Kazior
2013-08-08  8:16 ` [PATCH 2/4] ath10k: fix HTC endpoint worker starvation Michal Kazior
2013-08-08 10:12   ` Michal Kazior
2013-08-12 14:56     ` Kalle Valo
2013-08-08  8:16 ` [PATCH 3/4] ath10k: implement 802.3 SNAP rx decap type A-MSDU handling Michal Kazior
2013-08-12 14:55   ` Kalle Valo [this message]
2013-08-13  5:18     ` Michal Kazior
2013-08-08  8:16 ` [PATCH 4/4] ath10k: plug possible memory leak in WMI Michal Kazior
2013-08-13  5:59 ` [PATCH v2 0/4] ath10k: fixes Michal Kazior
2013-08-13  5:59   ` [PATCH v2 1/4] ath10k: fix HTT service setup Michal Kazior
2013-08-13  5:59   ` [PATCH v2 2/4] ath10k: fix HTC endpoint worker starvation Michal Kazior
2013-08-13 10:22     ` Michal Kazior
2013-08-13  5:59   ` [PATCH v2 3/4] ath10k: implement 802.3 SNAP rx decap type A-MSDU handling Michal Kazior
2013-08-13  5:59   ` [PATCH v2 4/4] ath10k: plug possible memory leak in WMI Michal Kazior
2013-08-14 15:02   ` [PATCH v2 0/4] ath10k: fixes Kalle Valo

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=878v07t0up.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=michal.kazior@tieto.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).