All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cao, Gang <gang.cao at intel.com>
To: spdk@lists.01.org
Subject: [SPDK] Re: Some questions about SPDK bdev module
Date: Thu, 10 Feb 2022 06:58:33 +0000	[thread overview]
Message-ID: <PH0PR11MB50143E32C714338DB5B39526832F9@PH0PR11MB5014.namprd11.prod.outlook.com> (raw)
In-Reply-To: 20220210044952.3721.72559@ml01.vlan13.01.org

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

https://github.com/spdk/spdk/blob/master/examples/bdev/fio_plugin/bdev.json is one example of JSON file which is to call the bdev_malloc_create() RPC method.

Basically it is to convert the RPC command to json format. You may refer this to change the log_set_flag RPC method to JSON content.

-----Original Message-----
From: liushengchao02(a)meituan.com <liushengchao02(a)meituan.com> 
Sent: Thursday, February 10, 2022 12:50
To: spdk(a)lists.01.org
Subject: [SPDK] Re: Some questions about SPDK bdev module

Thank you for the reply.

For the 1st question, is it certain that the SPDK framework will handle remaining uncompleted spdk_bdev_io?

For the 2nd question, what I want is an example of 'json config file' that would do the same thing as calling 'rpc.py log_set_flag nvme' when I start the SPDK app with '-c' option and specify the 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  6:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10  6:58 Cao, Gang [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 13:33 Luse, Paul E
2022-02-10  7:21 liushengchao02
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=PH0PR11MB50143E32C714338DB5B39526832F9@PH0PR11MB5014.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.