linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Fariya Fathima <fariya.f@redpinesignals.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 3.14.0-rc5 v3 3/10] rsi: Adding core and main files
Date: Wed, 05 Mar 2014 18:58:16 +0100	[thread overview]
Message-ID: <1394042296.5275.45.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <-1822952301-40502@mail.redpinesignals.com>

Hi,

[please don't send HTML emails, the list will drop those]

> In our code, we do fill in skb->priority field as you have seen. Once
> the pkt comes over to my driver, I thought I could over-write the
> priority field as I don't see this field being used again by the
> mac80211 stack. Even in case there is a failure and I call the
> ieee80211_free_txskb( ), I don't see that field being used.
> Considering this, can I not re-use the field within my driver or am I
> missing something in here?

No, I guess you can do that. However, there are cases where the packet
could potentially be reprocessed by mac80211, notably in the AP-side
code for handling powersave clients (ieee80211_sta_ps_deliver_response).
These code paths aren't executed for your driver right now, so this
isn't really a concern, but if you plan on adding AP/GO support then it
might be worth using a field inside skb->cb instead where you already
have other fields.

IOW, it's fine right now, but if you extend your code in the future you
may run into hard to debug issues with it.

johannes


       reply	other threads:[~2014-03-05 17:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <-1822952301-40502@mail.redpinesignals.com>
2014-03-05 17:58 ` Johannes Berg [this message]
2014-03-03  8:17 [PATCH 3.14.0-rc5 v3 3/10] rsi: Adding core and main files Fariya Fatima
2014-03-05 10:55 ` Johannes Berg
2014-03-05 10:56 ` Johannes Berg
2014-03-05 11:02 ` Johannes Berg

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=1394042296.5275.45.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=fariya.f@redpinesignals.com \
    --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 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).