From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Add py-spdk client for SPDK
Date: Fri, 26 Jan 2018 22:28:37 +0000 [thread overview]
Message-ID: <1517005716.25907.61.camel@intel.com> (raw)
In-Reply-To: CAHZqm+WnY2uifnq1wTQCYXTxR0e90sqq0H16n=PN2tgrNSF4OA@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]
On Wed, 2018-01-24 at 07:13 +0800, Zhipeng Huang wrote:
> Do we have a conclusion on this issue ? If it is ok to have a spdk/sdk repo,
> then wewe will modify the current patch (get rid of protobuff) and resubmit
> the patch to the new repo once it is established (meanwhile abandon the
> current one to spdk/spdk).
If you remove protobuf, can you describe what is left? Recently scripts/rpc.py
was refactored to break it up into a set of Python libraries in scripts/rpc,
plus the command line tool at scripts/rpc.py. What functionality does this new
code provide over and above what is already present there?
SPDK is certainly in need of better management tools, so in the most general
sense the community is very supportive of your effort here. New management tools
can also go directly into the main spdk repository (a separate repository was
only suggested when we thought this was a Python binding to the SPDK libraries).
I'm wondering if an easier way forward would be to continue refining the Python
packages in scripts/rpc to be more general purpose libraries for sending the
JSON RPCs. What are your thoughts on that?
next reply other threads:[~2018-01-26 22:28 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 22:28 Walker, Benjamin [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-28 2:06 [SPDK] Add py-spdk client for SPDK helloway
2018-02-08 13:54 Luse, Paul E
2018-02-08 8:52 We We
2018-02-06 4:07 Luse, Paul E
2018-02-06 3:35 We We
2018-02-05 19:20 Luse, Paul E
2018-02-05 9:20 We We
2018-01-27 21:25 Luse, Paul E
2018-01-27 7:11 Zhipeng Huang
2018-01-23 23:13 Zhipeng Huang
2018-01-18 22:57 Zhipeng Huang
2018-01-18 16:58 Walker, Benjamin
2018-01-18 16:05 Zhipeng Huang
2018-01-18 15:49 Walker, Benjamin
2018-01-18 15:42 Tushar Gohad
2018-01-18 15:12 We We
2018-01-18 14:22 Szwed, Maciej
2018-01-18 2:01 Zhipeng Huang
2018-01-18 1:49 Luse, Paul E
2018-01-18 1:40 Luse, Paul E
2018-01-18 1:32 Zhipeng Huang
2018-01-18 0:17 Luse, Paul E
2018-01-17 23:03 Zhipeng Huang
2018-01-17 21:39 Luse, Paul E
2018-01-17 17:25 We We
2018-01-17 14:32 Luse, Paul E
2018-01-17 12:24 We We
2018-01-16 15:53 Luse, Paul E
2018-01-16 3:30 We We
2018-01-11 6:16
2018-01-11 2:08 Zhipeng Huang
2018-01-11 1:56
2018-01-11 1:46 Zhipeng Huang
2018-01-11 1:37 Luse, Paul E
2018-01-10 13:46 We We
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=1517005716.25907.61.camel@intel.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.