From: Ben Greear <greearb@candelatech.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: How to best consolidate list of skbs (msdu) for receive?
Date: Thu, 27 Feb 2014 10:36:30 -0800 [thread overview]
Message-ID: <530F85AE.8060002@candelatech.com> (raw)
In ath10k, it can receive msdu (in rx raw mode, at least). These show up
as a list of skb. Currently they are just dropped as un-handled, and I
need to fix this.
I think I need to consolidate this list into a single skb in order to pass
it up the stack.
What is the preferred way to go about doing this?
It seems I could just expand the head skb (pskb_expand_head) and copy the data from the others
onto the end of the head skb, but maybe there is a more efficient way to go about
doing this?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2014-02-27 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 18:36 Ben Greear [this message]
2014-02-27 20:37 ` How to best consolidate list of skbs (msdu) for receive? Florian Fainelli
2014-02-27 21:21 ` Eric Dumazet
2014-02-27 21:51 ` Ben Greear
2014-02-27 22:31 ` Eric Dumazet
2014-02-27 22:38 ` Ben Greear
2014-02-27 23:03 ` Eric Dumazet
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=530F85AE.8060002@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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 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).