From: Tony Asleson <tasleson@redhat.com>
To: Sagi Grimberg <sagi@grimberg.me>, linux-nvme@lists.infradead.org
Subject: Re: nvmet and stable API
Date: Wed, 1 Apr 2020 11:34:34 -0500 [thread overview]
Message-ID: <cae7b76c-06a4-d870-22d5-ec09cd57354d@redhat.com> (raw)
In-Reply-To: <c89ef694-b447-5e2e-429c-bc449b3c57b4@grimberg.me>
On 3/25/20 1:58 AM, Sagi Grimberg wrote:
> We don't have an API for python. I sort of assumed that this will
> be contributed by the people that want/need it.
Maybe, I'm interpreting this statement incorrectly, if so please
clarify. I'm reading this as write what you need for whatever language
to configfs. This works and it's not difficult to do, but what to do
for persistence?
Try to write compatible JSON output across code bases and supported
kernel features? Have everyone fork & exec "nvmetcli save"? Write out
your own file and document not to use incompatible stacks?
Additionally, none of this addresses a potential race condition between
two or more processes with different implementations making concurrent
changes to configfs and getting the configuration saved with no lost
changes.
Suggestions?
Thanks,
Tony
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-04-01 16:34 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
2020-04-01 16:34 ` Tony Asleson [this message]
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=cae7b76c-06a4-d870-22d5-ec09cd57354d@redhat.com \
--to=tasleson@redhat.com \
--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