From: Sagi Grimberg <sagi@grimberg.me>
To: tasleson@redhat.com, linux-nvme@lists.infradead.org
Subject: Re: nvmet and stable API
Date: Tue, 24 Mar 2020 23:58:02 -0700 [thread overview]
Message-ID: <c89ef694-b447-5e2e-429c-bc449b3c57b4@grimberg.me> (raw)
In-Reply-To: <d4060208-ec69-3211-277c-d151be302555@redhat.com>
> With the existing functionality of nvmetcli in that you can
> save/restore/clear/ls and use interactively seems to indicate that if
> you want to programmaticlly change the state of targets that you need to
> use the python code that is available in nvmet which is used by the CLI.
nvmetcli needs to be backward compatible with kernels lacking
functionality. Anywhere this is not the case, its a bug and we need
to fix it.
> Is this a correct assumption, that nvmet is an API for external python
> programs to use?
We don't have an API for python. I sort of assumed that this will
be contributed by the people that want/need it.
> The block tests in https://github.com/osandov/blktests.git seem to
> indicate that going straight to configfs is the API?
That's for dependency minimization.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-03-25 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 18:15 nvmet and stable API Tony Asleson
2020-03-25 6:58 ` Sagi Grimberg [this message]
2020-04-01 16:34 ` Tony Asleson
2020-04-03 6:53 ` 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=c89ef694-b447-5e2e-429c-bc449b3c57b4@grimberg.me \
--to=sagi@grimberg.me \
--cc=linux-nvme@lists.infradead.org \
--cc=tasleson@redhat.com \
/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).