All of lore.kernel.org
 help / color / mirror / Atom feed
From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Question about SPDK
Date: Thu, 15 Sep 2016 15:13:33 +0000	[thread overview]
Message-ID: <1473952412.2810.97.camel@intel.com> (raw)
In-Reply-To: d7330829-2875-4658-ae53-ee67d31c7f9c@ww-it.cn

[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]

On Thu, 2016-09-15 at 09:27 +0800, ZHU XIAN WEN wrote:
> hello all
> 
> I had simple questions about SPDK:
> 
> does SPDK support FreeBSD? or it just support Linux only?

SPDK supports FreeBSD where possible. Our NVMe driver and our I/OAT driver work,
as does our iSCSI target, but our NVMe-oF target requires a functional
libibverbs which isn't available on FreeBSD. If that dependency was available,
our target should work.
> 
> for Linux, which kernel version is adviced to run SPDK?

SPDK uses a very small number of kernel interfaces, so you are free to choose
essentially any "modern" Linux kernel starting with the 3.x series. We do most
of our testing closer to the latest - 4.6 as of this email - but we run this on
3.x kernels regularly too. The main requirement is that the kernel supports
either uio or vfio. If you ever run into a problem on an older kernel we'd love
to hear about it so we can fix it.
> 
> 
> best wishes
> 
> 
> Tony
> 
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk

             reply	other threads:[~2016-09-15 15:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15 15:13 Walker, Benjamin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-09-15  1:27 [SPDK] Question about SPDK ZHU XIAN WEN

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=1473952412.2810.97.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.