From: David Miller <davem@davemloft.net>
To: raj@tardy.usa.hp.com
Cc: netdev@vger.kernel.org, sathya.perla@emulex.com,
subbu.seetharaman@emulex.com, ajit.khaparde@emulex.com
Subject: Re: [PATCH net-next] be2net: Use dev_consume_skb_any() in the non-drop path
Date: Fri, 29 Aug 2014 20:37:15 -0700 (PDT) [thread overview]
Message-ID: <20140829.203715.926250452196304335.davem@davemloft.net> (raw)
In-Reply-To: <20140828155316.5AE982900409@tardy>
From: raj@tardy.usa.hp.com (Rick Jones)
Date: Thu, 28 Aug 2014 08:53:16 -0700 (PDT)
> From: Rick Jones <rick.jones2@hp.com>
>
> The be2net driver was still using dev_kfree_skb_any() in a "normal"
> skb freeing path. This rather clutters perf top -G -e skb_kfree_skb
> profiling.
>
> Signed-off-by: Rick Jones <rick.jones2@hp.com>
Applied, thanks Rick.
prev parent reply other threads:[~2014-08-30 3:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 15:53 [PATCH net-next] be2net: Use dev_consume_skb_any() in the non-drop path Rick Jones
2014-08-30 3:37 ` David Miller [this message]
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=20140829.203715.926250452196304335.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ajit.khaparde@emulex.com \
--cc=netdev@vger.kernel.org \
--cc=raj@tardy.usa.hp.com \
--cc=sathya.perla@emulex.com \
--cc=subbu.seetharaman@emulex.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).