All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luse, Paul E <paul.e.luse at intel.com>
To: spdk@lists.01.org
Subject: [SPDK] Re: Some questions about SPDK bdev module
Date: Thu, 10 Feb 2022 13:33:56 +0000	[thread overview]
Message-ID: <CO1PR11MB48364BAD41D325146F421864AD2F9@CO1PR11MB4836.namprd11.prod.outlook.com> (raw)
In-Reply-To: 20220210072139.3721.70563@ml01.vlan13.01.org

[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]

Hi,

The example that Gang provided looked pretty good, you just need to use that format and change the keys/values.  Can you provide the exact json file that you’ve tried (mentioned below) that isn’t working?

Thx
Paul

From: liushengchao02(a)meituan.com <liushengchao02(a)meituan.com>
Date: Thursday, February 10, 2022 at 12:22 AM
To: spdk(a)lists.01.org <spdk(a)lists.01.org>
Subject: [SPDK] Re: Some questions about SPDK bdev module
Thank you for the reply.

I have tested many ways in a "json config file" but still can not work as executing 'rpc.py log_set_flag nvme' when starting the SPDK app with '-c' option and specify the json config file.

That's why I'm here asking for an example of "json config file".

Does anybody know the answers? Or currently SPDK does not support "log_set_flag" in a json config file?

Thanks
_______________________________________________
SPDK mailing list -- spdk(a)lists.01.org
To unsubscribe send an email to spdk-leave(a)lists.01.org

             reply	other threads:[~2022-02-10 13:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 13:33 Luse, Paul E [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-11 12:37 [SPDK] Re: Some questions about SPDK bdev module Luse, Paul E
2022-02-11 12:36 liushengchao02
2022-02-11 12:30 liushengchao02
2022-02-10 15:14 Harris, James R
2022-02-10  7:21 liushengchao02
2022-02-10  6:58 Cao, Gang
2022-02-10  4:49 liushengchao02
2022-02-10  4:26 Cao, Gang

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=CO1PR11MB48364BAD41D325146F421864AD2F9@CO1PR11MB4836.namprd11.prod.outlook.com \
    --to=spdk@lists.01.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.