public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: David Miller <davem@davemloft.net>
Cc: tomasw@gmail.com, linville@tuxdriver.com, netdev@vger.kernel.org,
	linux-wireless@vger.kernel.org
Subject: Re: [RFC v2] mac80211: assign needed_headroom/tailroom for netdevs
Date: Tue, 06 May 2008 01:23:55 +0200	[thread overview]
Message-ID: <1210029835.8012.30.camel@johannes.berg> (raw)
In-Reply-To: <20080505.161458.46071527.davem@davemloft.net>

[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]

On Mon, 2008-05-05 at 16:14 -0700, David Miller wrote:

> > Right, that makes sense. But will it ever return false? skb_cloned()
> > returns true often enough, and we only accept linear skbs, but I think I
> > don't understand yet what skb_header_cloned() vs. skb_cloned() refers
> > to. Which exactly is the header space I'm allowed to modify when
> > skb_header_cloned() returns false?
> 
> skb_header_cloned() will return false always if the buffer is not
> cloned.

Right, it's less than skb_cloned().

> If it is cloned, it makes sure the data reference count allows
> for modification of the buffer.

Which buffer? skb->data..skb->tail? And isn't that, in mac80211's case,
at least currently all the buffer anyway?

> For normal traffic, you should see skb_header_cloned() always return
> false unless a network tap like tcpdump is registered.

Interesting point. I'll have to see when socket filters are run,
wpa_supplicant could have a tap open I think. Maybe that's why I'm
seeing so many cloned packets. I think I'll stacktrace skb_clone and
print that out.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2008-05-05 23:24 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-04 21:24 [RFC] mac80211: assign needed_headroom/tailroom for netdevs Johannes Berg
2008-05-04 21:31 ` Johannes Berg
2008-05-04 21:32 ` [RFC v2] " Johannes Berg
2008-05-05  0:30   ` David Miller
2008-05-05  7:22     ` Johannes Berg
2008-05-05 14:27       ` Tomas Winkler
2008-05-05 15:22         ` Johannes Berg
2008-05-05 17:15           ` Tomas Winkler
2008-05-05 17:57             ` Johannes Berg
2008-05-05 18:58               ` David Miller
2008-05-05 19:05                 ` Johannes Berg
2008-05-05 19:50                   ` David Miller
2008-05-05 19:57                     ` Johannes Berg
2008-05-05 20:02                       ` David Miller
2008-05-05 20:10                         ` Johannes Berg
2008-05-05 20:44                           ` David Miller
2008-05-05 20:57                             ` Johannes Berg
2008-05-05 21:01                               ` David Miller
2008-05-05 22:37                               ` David Miller
2008-05-05 22:44                                 ` Johannes Berg
2008-05-05 23:14                                   ` David Miller
2008-05-05 23:23                                     ` Johannes Berg [this message]
2008-05-05 23:39                                       ` David Miller
2008-05-06  0:01                                         ` Johannes Berg
2008-05-06  0:08                                           ` David Miller
2008-05-06 11:13                                             ` Johannes Berg
2008-05-06  1:32                                         ` Herbert Xu
2008-05-13  5:01                                 ` David Miller
2008-05-05 23:03           ` David Miller
2008-05-05 23:17             ` Johannes Berg
2008-05-05 23:24               ` David Miller
2008-05-05 23:30                 ` Johannes Berg
2008-05-05 23:36             ` Johannes Berg
2008-05-05 23:40               ` David Miller
2008-05-13  3:52   ` David Miller
2008-05-13  9:01     ` Johannes Berg
2008-05-13  9:45       ` David Miller
2008-05-13 10:07         ` 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=1210029835.8012.30.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=davem@davemloft.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=tomasw@gmail.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