Return-path: Received: from sabertooth02.qualcomm.com ([65.197.215.38]:50554 "EHLO sabertooth02.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756228Ab3HLO4F (ORCPT ); Mon, 12 Aug 2013 10:56:05 -0400 From: Kalle Valo To: Michal Kazior CC: , Subject: Re: [PATCH 3/4] ath10k: implement 802.3 SNAP rx decap type A-MSDU handling References: <1375949813-10969-1-git-send-email-michal.kazior@tieto.com> <1375949813-10969-4-git-send-email-michal.kazior@tieto.com> Date: Mon, 12 Aug 2013 17:55:42 +0300 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") Message-ID: <878v07t0up.fsf@kamboji.qca.qualcomm.com> (sfid-20130812_165610_762887_683AF877) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: linux-wireless-owner@vger.kernel.org List-ID: Michal Kazior 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 [...] > @@ -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