From: Nguyen, Anthony L <anthony.l.nguyen@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next v2] ice: add tracepoints
Date: Tue, 8 Jun 2021 23:08:08 +0000 [thread overview]
Message-ID: <1e972693734fc6c19fc03b74cb3037b0a4f42852.camel@intel.com> (raw)
In-Reply-To: <20210608092705.00005761@intel.com>
On Tue, 2021-06-08 at 09:27 -0700, Jesse Brandeburg wrote:
> Jesse Brandeburg wrote:
>
> > This patch is modeled after one by Scott Peterson for i40e.
>
> I found a little bug in the code, Tony do you want to correct it or
> have me send a v3?
A v3 would be preferable.
Thanks,
Tony
> > +DECLARE_EVENT_CLASS(ice_tx_dim_template,
> > + TP_PROTO(struct ice_q_vector *q_vector, struct dim
> > *dim),
> > + TP_ARGS(q_vector, dim),
> > + TP_STRUCT__entry(__field(struct ice_q_vector *,
> > q_vector)
> > + __field(struct dim *, dim)
> > + __string(devname, q_vector-
> > >tx.ring->netdev->name)),
> > +
> > + TP_fast_assign(__entry->q_vector = q_vector;
> > + __entry->dim = dim;
> > + __assign_str(devname, q_vector-
> > >tx.ring->netdev->name);),
> > +
> > + TP_printk("netdev: %s Tx-Q: %d dim-state: %d dim-
> > profile: %d dim-tune: %d dim-st-right: %d dim-st-left: %d dim-
> > tired: %d",
> > + __get_str(devname),
> > + __entry->q_vector->rx.ring->q_index,
>
> should be: tx.ring
>
> _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan at osuosl.org
> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2021-06-08 23:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 1:49 [Intel-wired-lan] [PATCH net-next v2] ice: add tracepoints Jesse Brandeburg
2021-06-08 16:27 ` Jesse Brandeburg
2021-06-08 23:08 ` Nguyen, Anthony L [this message]
2021-06-08 23:36 ` Jesse Brandeburg
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=1e972693734fc6c19fc03b74cb3037b0a4f42852.camel@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@osuosl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.