From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Aya Levin <ayal@mellanox.com>
Cc: netdev@vger.kernel.org, Eran Ben Elisha <eranbe@mellanox.com>,
Saeed Mahameed <saeedm@mellanox.com>,
Jiri Pirko <jiri@mellanox.com>
Subject: Re: [PATCH net-next RFC] Dump SW SQ context as part of tx reporter
Date: Mon, 29 Apr 2019 20:54:41 -0400 [thread overview]
Message-ID: <20190429205441.13c34785@cakuba> (raw)
In-Reply-To: <1556547459-7756-1-git-send-email-ayal@mellanox.com>
On Mon, 29 Apr 2019 17:17:39 +0300, Aya Levin wrote:
> In order to offline translate the raw memory into a human readable
> format, the user can use some out-of-kernel scripts which receives as an
> input the following:
> - Object raw memory
> - Driver object compiled with debug info (can be taken/generated at any time from the machine)
> - Object name
Nice! IMHO this is more clean, precise and scalable than the fmsg stuff
that we have now.
Would you mind taking the string identifiers down a little bit more?
"memory" could just have a first-class netlink attribute, it doesn't
have to be this fake JSON string pair..
next prev parent reply other threads:[~2019-04-30 0:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 14:17 [PATCH net-next RFC] Dump SW SQ context as part of tx reporter Aya Levin
2019-04-29 18:32 ` Saeed Mahameed
2019-04-30 11:13 ` Aya Levin
2019-04-30 0:54 ` Jakub Kicinski [this message]
2019-04-30 11:26 ` Aya Levin
2019-05-07 12:41 ` Jiri Pirko
2019-05-07 12:58 ` Aya Levin
2019-05-09 8:23 ` Jiri Pirko
2019-05-12 8:37 ` Aya Levin
2019-05-14 12:07 ` Jiri Pirko
2019-05-16 8:49 ` Aya Levin
2019-05-16 11:53 ` Jiri Pirko
2019-05-16 12:02 ` Aya Levin
-- strict thread matches above, loose matches on Subject: below --
2019-05-16 22:06 Jakub Kicinski
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=20190429205441.13c34785@cakuba \
--to=jakub.kicinski@netronome.com \
--cc=ayal@mellanox.com \
--cc=eranbe@mellanox.com \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.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 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.