From: David Miller <davem@davemloft.net>
To: jiri@resnulli.us
Cc: netdev@vger.kernel.org, eladr@mellanox.com, idosch@mellanox.com
Subject: Re: HW communication debugging interface - ideas?
Date: Sun, 01 Nov 2015 11:51:16 -0500 (EST) [thread overview]
Message-ID: <20151101.115116.620913426492186507.davem@davemloft.net> (raw)
In-Reply-To: <20150930135141.GF2098@nanopsycho.orion>
From: Jiri Pirko <jiri@resnulli.us>
Date: Wed, 30 Sep 2015 15:51:41 +0200
> 2) generic Netlink (genl) interface. Easy to put metadata in, including the
> device identificator (pci address). User then can use nlmon in order to
> be able to use wireshark to see the netlink messages.
>
> Looks like 2) might be viable, well-defined, generic interface to carry
> this info. What do you think? Does this make sense?
Sorry for the late response. I definitely prefer this netlink idea,
particularly for the metadata aspect.
Yes, the ethernet frames should "identify" the device, but I much more
like the idea of precisely having the geographic ID of the device (PCI
ID, whatever) available as metadata as well.
next prev parent reply other threads:[~2015-11-01 16:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 13:51 HW communication debugging interface - ideas? Jiri Pirko
2015-10-05 8:54 ` Jiri Pirko
2015-10-05 9:38 ` David Miller
2015-10-05 9:45 ` Jiri Pirko
2015-10-05 9:54 ` Rosen, Rami
2015-10-05 9:56 ` Jiri Pirko
2015-10-05 14:49 ` Andrew Lunn
2015-10-05 14:55 ` Jiri Pirko
2015-10-05 14:58 ` Andrew Lunn
2015-10-05 15:18 ` Jiri Pirko
2015-10-05 15:29 ` John Fastabend
2015-10-05 15:35 ` Jiri Pirko
2015-10-05 15:47 ` John Fastabend
2015-10-06 8:14 ` Jiri Pirko
2015-10-06 14:54 ` John Fastabend
2015-10-06 15:02 ` Jiri Pirko
2015-10-06 15:02 ` Andrew Lunn
2015-11-01 17:58 ` Guy Harris
2015-10-05 12:28 ` Thomas Graf
2015-10-05 18:32 ` Marcelo Ricardo Leitner
2015-10-05 20:40 ` Jiri Pirko
2015-11-01 16:51 ` David Miller [this message]
2015-11-02 6:13 ` Jiri Pirko
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=20151101.115116.620913426492186507.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eladr@mellanox.com \
--cc=idosch@mellanox.com \
--cc=jiri@resnulli.us \
--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;
as well as URLs for NNTP newsgroup(s).