From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: netdev@vger.kernel.org, linux-net-drivers@solarflare.com
Subject: Re: [PATCH net-next 0/3] Improve tracing at the driver/core boundary
Date: Tue, 14 Jan 2014 14:47:23 -0800 (PST) [thread overview]
Message-ID: <20140114.144723.957109797286173047.davem@davemloft.net> (raw)
In-Reply-To: <1389392139.2025.123.camel@bwh-desktop.uk.level5networks.com>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Fri, 10 Jan 2014 22:15:39 +0000
> These patches add static tracpeoints at the driver/core boundary which
> record various skb fields likely to be useful for datapath debugging.
> On the TX side the boundary is where the core calls ndo_start_xmit, and
> on the RX side it is where any of the various exported receive functions
> is called.
>
> The set of skb fields is mostly based on what I thought would be
> interesting for sfc.
>
> These patches are basically the same as what I sent as an RFC in
> November, but rebased. They now depend on 'net: core: explicitly select
> a txq before doing l2 forwarding', so please merge net into net-next
> before trying to apply them. The first patch fixes a code formatting
> error left behind after that fix.
This looks great, series applied, thanks Ben.
prev parent reply other threads:[~2014-01-14 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 22:15 [PATCH net-next 0/3] Improve tracing at the driver/core boundary Ben Hutchings
2014-01-10 22:16 ` [PATCH net-next 1/3] net: Fix indentation in dev_hard_start_xmit() Ben Hutchings
2014-01-10 22:17 ` [PATCH net-next 2/3] net: Add net_dev_start_xmit trace event, exposing more skb fields Ben Hutchings
2014-01-10 22:17 ` [PATCH net-next 3/3] net: Add trace events for all receive entry points, " Ben Hutchings
2014-01-14 22:47 ` 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=20140114.144723.957109797286173047.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@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