From: E.W.Z. <kreuzerkrieg at gmail.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] SPDK build and submodules
Date: Sun, 10 Mar 2019 23:00:28 +0200 [thread overview]
Message-ID: <5c857aed.1c69fb81.7181e.f436@mx.google.com> (raw)
In-Reply-To: 82C9F782B054C94B9FC04A331649C77AB8D15644@FMSMSX126.amr.corp.intel.com
[-- Attachment #1: Type: text/plain, Size: 2303 bytes --]
Thanks Paul, sure it helps, but I see there is a serious problem, it is not vanilla repo of isal/ipsec/DPDK, so,I guess, I cant just clone original repository of these three above and hope it will work fine with SPDK. It make stuff more complicated, but I guess it is still doable.
Thanks again!
Sent from Mail for Windows 10
From: Luse, Paul E
Sent: Sunday, March 10, 2019 22:32
To: Storage Performance Development Kit
Subject: Re: [SPDK] SPDK build and submodules
Hi Ernest,
Each submodule points to a fork of one of the applicable repo that are all stored here: https://github.com/spdk
To determine the version, you can use 'git submodule' from the root and it will show you both the hash that the submodule is pointing to and the version information.
git submodule
67b915b09bcf51ae2e2a703718881f0b0845883c dpdk (v18.08-1994-g67b915b09)
134c90c912ea9376460e9d949bb1319a83a9d839 intel-ipsec-mb (v0.49-1-g134c90c)
09e787231b31add1234ec9a3dfe718533f1c3bf4 isa-l (v2.24.0-3-g09e7872)
We carry these forks so that, if needed, we can apply patches that we need prior to them making it into the upstream repo. DPDK is usually updated w/every release and ipsec and isal will be updated as needed. In fact I'm going to update ipsec soon because a newer version is needed for one of the crypto drivers.
Anyway, hope that helps....
Thx
Paul
-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of E.W.Z.
Sent: Sunday, March 10, 2019 1:20 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org> <spdk(a)lists.01.org>
Subject: [SPDK] SPDK build and submodules
Hi,
Consider following limitation when building SPDK, no submodules can be used, but I can build isa-l/ipsec/DPDK outside of SPDK tree. What kind of submodules versioning scheme is used? For example, SPDK 19.01, how it connects to releases of the other three modules? Latest releases of these at the moment the 19.01 is delivered? Where can I get this info? Thanks!
Sincerely,
Ernest
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk
next reply other threads:[~2019-03-10 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 21:00 E.W.Z. [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-10 20:32 [SPDK] SPDK build and submodules Luse, Paul E
2019-03-10 20:20 E.W.Z.
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=5c857aed.1c69fb81.7181e.f436@mx.google.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.