From: "David S. Miller" <davem@davemloft.net>
To: shemminger@osdl.org
Cc: ranjitm@google.com, akpm@osdl.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] tcpdump may trace some outbound packets twice.
Date: Mon, 15 May 2006 17:08:35 -0700 (PDT) [thread overview]
Message-ID: <20060515.170835.126804002.davem@davemloft.net> (raw)
In-Reply-To: <20060515164101.054afa29@localhost.localdomain>
From: Stephen Hemminger <shemminger@osdl.org>
Date: Mon, 15 May 2006 16:41:01 -0700
> kfree_skb(NULL) is legal so the conditional here is unneeded.
>
> But the increased calls to kfree_skb(NULL) would probably bring the
> "unlikely()" hordes descending on kfree_skb, so maybe:
And unfortunately as Patrick McHardy states, we can't use
this trick here because things like tc actions can do stuff
like pskb_expand_head() which cannot handle shared SKBs.
We need another solution to this problem, because cloning an
extra SKB is just rediculious overhead so isn't something we
can seriously consider to solve this problem.
Another option is to say this anomaly doesn't matter enough
to justify the complexity we're looking at here just to fix
this glitch.
Other implementation possibility suggestions welcome :-)
next prev parent reply other threads:[~2006-05-16 0:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 20:17 Ranjit Manomohan
2006-05-14 10:10 ` Andrew Morton
2006-05-14 15:58 ` Ranjit Manomohan
2006-05-14 20:42 ` David S. Miller
2006-05-15 21:19 ` Ranjit Manomohan
2006-05-15 21:26 ` David S. Miller
2006-05-15 21:41 ` Patrick McHardy
2006-05-15 23:11 ` Ranjit Manomohan
2006-05-15 23:41 ` Stephen Hemminger
2006-05-16 0:08 ` David S. Miller [this message]
2006-05-16 0:21 ` Patrick McHardy
2006-05-16 0:48 ` Tom Young
2006-05-16 0:37 ` Herbert Xu
2006-05-16 1:17 ` Patrick McHardy
2006-05-16 1:20 ` Herbert Xu
2006-05-16 1:22 ` Patrick McHardy
2006-05-16 4:18 ` David S. Miller
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=20060515.170835.126804002.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ranjitm@google.com \
--cc=shemminger@osdl.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
all inboxes | Powered by JetHome®