From: Junchang Wang <junchangwang@gmail.com>
To: Changli Gao <xiaosuo@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <eric.dumazet@gmail.com>,
Tom Herbert <therbert@google.com>, Jiri Pirko <jpirko@redhat.com>,
Fenghua Yu <fenghua.yu@intel.com>,
Xinan Tang <xinan.tang@intel.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH] net: increase skb->users instead of skb_clone()
Date: Thu, 16 Dec 2010 22:05:01 +0800 [thread overview]
Message-ID: <AANLkTikdYi-Cs=4UtjJx-X4bW+LSKTQBTcSv23NS2S+S@mail.gmail.com> (raw)
In-Reply-To: <1292479045-3136-1-git-send-email-xiaosuo@gmail.com>
On Thu, Dec 16, 2010 at 1:57 PM, Changli Gao <xiaosuo@gmail.com> wrote:
> In dev_queue_xmit_nit(), we have to clone skbs as we need to mangle skbs,
> however, we don't need to clone skbs for all the packet_types.
>
> Except for the first packet_type, we increase skb->users instead of
> skb_clone().
Hi Changli,
Take af_packet for example, I can't see benefit from this patch.
> +static inline int deliver_skb(struct sk_buff *skb,
> + struct packet_type *pt_prev,
> + struct net_device *orig_dev)
> +{
> + atomic_inc(&skb->users);
> + return pt_prev->func(skb, skb->dev, pt_prev, orig_dev);
> +}
The increment call will incur skb_shared() failure in packet_rcv.
In reality, packet_rcv has to clone this packet by itself.
Thanks
--
--Junchang
next prev parent reply other threads:[~2010-12-16 14:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 5:57 [PATCH] net: increase skb->users instead of skb_clone() Changli Gao
2010-12-16 7:18 ` Eric Dumazet
2010-12-16 7:23 ` Changli Gao
2010-12-16 7:50 ` Eric Dumazet
2010-12-16 14:20 ` Junchang Wang
2010-12-16 14:30 ` Eric Dumazet
2010-12-16 14:05 ` Junchang Wang [this message]
2010-12-16 14:12 ` Changli Gao
2010-12-16 14:36 ` Junchang Wang
2010-12-16 14:18 ` Eric Dumazet
2010-12-16 14:31 ` Junchang Wang
2010-12-16 14:41 ` Eric Dumazet
2010-12-16 14:43 ` Changli Gao
2010-12-17 0:24 ` Junchang Wang
2010-12-20 5:50 ` David 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='AANLkTikdYi-Cs=4UtjJx-X4bW+LSKTQBTcSv23NS2S+S@mail.gmail.com' \
--to=junchangwang@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=fenghua.yu@intel.com \
--cc=jpirko@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.com \
--cc=xiaosuo@gmail.com \
--cc=xinan.tang@intel.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;
as well as URLs for NNTP newsgroup(s).