From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] vpp 18.10 with spdk
Date: Thu, 14 Mar 2019 19:07:27 +0000 [thread overview]
Message-ID: <2bad342c377f3f619e72c36ddd93a487027d8412.camel@intel.com> (raw)
In-Reply-To: f166a0e7f81ca757baad1e2ca04a4fd8@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]
On Wed, 2019-03-13 at 12:09 -0700, Jonathan Richardson wrote:
> Hi,
>
>
>
> Just wondering if there is any plan to support a newer version of vpp. I
> want to use vpp 18.10 so will upgrade the spdk code. It looks like the vpp
> version tags are similar to SPDK. Is there any reason why the vpp support
> isn’t newer? If not I’ll upstream my changes when done. Do you have any
> guidelines on backwards compatibility should the version used by spdk be
> made configurable?
>
The only reason VPP hasn't been upgraded is that no one has done it yet. If
you'd like to tackle the upgrade, please do submit the patches. That would be
great!
In general SPDK does have a number of backward compatibility requirements.
However, for VPP specifically, I don't see any downside to just doing a
wholesale upgrade this time. I don't think you need to maintain backward
compatibility with an older VPP.
Thanks,
Ben
>
>
> Thanks,
>
> Jon
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
next reply other threads:[~2019-03-14 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 19:07 Walker, Benjamin [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-27 0:29 [SPDK] vpp 18.10 with spdk Jonathan Richardson
2019-03-13 19:09 Jonathan Richardson
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=2bad342c377f3f619e72c36ddd93a487027d8412.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox