public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: alan.adamson@oracle.com
To: Sagi Grimberg <sagi@grimberg.me>, linux-nvme@lists.infradead.org
Cc: kbusch@kernel.org, hch@lst.de
Subject: Re: [RFC v3 1/1] nvme: add passthrough error logging opt-in
Date: Mon, 3 Apr 2023 15:54:52 -0700	[thread overview]
Message-ID: <935faecc-e000-3d7a-71ed-7517b1f4c299@oracle.com> (raw)
In-Reply-To: <132431e1-6c77-4e4d-1d48-fbb0bd4dc5b6@grimberg.me>


On 4/3/23 3:38 PM, Sagi Grimberg wrote:
>
>>>> +    if (!nr->ctrl->error_logging)
>>>> +        req->rq_flags |= RQF_QUIET;
>>>> +
>>>> +    memcpy(nr->cmd, cmd, sizeof(*cmd));
>>>
>>> Question, if we already introduce granularity to this setting, why
>>> not per-ns? why only per controller? I'd think it makes more
>>> sense to do this per ns. Will also remove access to ctrl in the hot
>>> path...
>>
>>
>> Meaning we should have both:
>>
>> /sys/class/nvme/nvme0/passthrough_logging
>>
>> /sys/class/nvme/nvme0/nvme0n1/passthrough_logging
>
> No, just the namespace logging, why would we need the
> controller as well?

For Admin Commands?

Alan




  reply	other threads:[~2023-04-03 22:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 22:18 [RFC v3 0/1] nvme: add passthrough error logging opt-in Alan Adamson
2023-03-31 22:18 ` [RFC v3 1/1] " Alan Adamson
2023-04-03  8:26   ` Pankaj Raghav
2023-04-05 22:35     ` alan.adamson
2023-04-06  4:13       ` Minwoo Im
2023-04-06  4:24         ` Chaitanya Kulkarni
2023-04-06  4:27           ` Minwoo Im
2023-04-03 10:17   ` Sagi Grimberg
2023-04-03 22:20     ` alan.adamson
2023-04-03 22:38       ` Sagi Grimberg
2023-04-03 22:54         ` alan.adamson [this message]
2023-04-03 23:29           ` Sagi Grimberg
2023-04-04 16:20             ` alan.adamson
2023-04-05 15:07               ` Christoph Hellwig

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=935faecc-e000-3d7a-71ed-7517b1f4c299@oracle.com \
    --to=alan.adamson@oracle.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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