Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: jthumshirn@suse.de (Johannes Thumshirn)
Subject: [PATCH 1/1] nvme: add get-feature to admin cmds tracer
Date: Fri, 8 Feb 2019 09:49:47 +0100	[thread overview]
Message-ID: <c4db17c4-c9fb-cf79-12ae-e2d3ceab123a@suse.de> (raw)
In-Reply-To: <20190208084216.GA23155@lst.de>

On 08/02/2019 09:42, Christoph Hellwig wrote:
> I don't really care.  We clearly have command decoding in the trace
> points, so adding a little more won't hurt, but I'm also not sure
> we really need it.

Hmm one thing, *iff* we want to decode the commands in user-space we
have to agree on one input format for the decoder which then becomes an
ABI (see for example blktrace). If we decode in the kernel we can easily
extent it (like we already did with the tracepoints).

IMHO maintaining an ABI like format is a major pain in the lower body
parts and the benefits from it aren't worth it.

Just my .2$.

Byte,
	Johannes
-- 
Johannes Thumshirn                            SUSE Labs Filesystems
jthumshirn at suse.de                                +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850

  reply	other threads:[~2019-02-08  8:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31 15:13 [PATCH 1/1] nvme: add get-feature to admin cmds tracer Max Gurtovoy
2019-01-31 16:11 ` Keith Busch
2019-01-31 17:01   ` Max Gurtovoy
2019-02-04  8:23     ` Johannes Thumshirn
2019-02-07 10:28       ` Max Gurtovoy
2019-02-08  8:42         ` Christoph Hellwig
2019-02-08  8:49           ` Johannes Thumshirn [this message]
2019-02-08 15:30             ` Keith Busch
2019-02-08 15:39               ` Johannes Thumshirn

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=c4db17c4-c9fb-cf79-12ae-e2d3ceab123a@suse.de \
    --to=jthumshirn@suse.de \
    /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