All of lore.kernel.org
 help / color / mirror / Atom feed
From: piaojun <piaojun@huawei.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: virtio-fs@redhat.com
Subject: Re: [Virtio-fs] Achieving parallelism in virtiofsd
Date: Fri, 5 Jul 2019 16:22:14 +0800	[thread overview]
Message-ID: <5D1F08B6.8000900@huawei.com> (raw)
In-Reply-To: <20190705080401.GC10995@stefanha-x1.localdomain>



On 2019/7/5 16:04, Stefan Hajnoczi wrote:
> On Fri, Jul 05, 2019 at 12:43:16PM +0800, piaojun wrote:
>> From your description, virtiofsd does the same work as SPDK, and I
>> wonder if we could adapt it to SPDK-vhost-fs which is widely used.
> 
> I don't see 9P code in spdk.git/master.  How does the guest access
> SPDK's vhost-fs device and where is the code?

Yes, 9P code is not in spdk yet, and they can comunicate though share
memory. But it needs some extra work.

> 
> A quick look at blobfs suggests additional work is needed to introduce
> the concept of inodes instead of performing path name traversal on most
> operations.  This also changes the semantics of the file system since
> POSIX files can still be accessed after they are unlinked or renamed.
> 
> In theory SPDK can implement the vhost-user-fs device interface and
> replace virtiofsd but SPDK needs a POSIX file system implementation
> first.

Right, SPDK could only support blobfs now, and I wish it supporting any
local file system as backend in the future. SPDK vhost-fs patches is in
developing as below:

https://review.gerrithub.io/c/spdk/spdk/+/449163/5
https://review.gerrithub.io/c/spdk/spdk/+/449162/5

Thanks,
Jun

> 
> Stefan
> 


  parent reply	other threads:[~2019-07-05  8:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04 10:46 [Virtio-fs] Achieving parallelism in virtiofsd Stefan Hajnoczi
2019-07-05  4:43 ` piaojun
2019-07-05  8:04   ` Stefan Hajnoczi
2019-07-05  8:14     ` Peng Tao
2019-07-05  9:56       ` Liu, Changpeng
2019-07-05  8:22     ` piaojun [this message]
2019-07-08 13:55 ` Vivek Goyal
2019-07-08 15:08 ` Dr. David Alan Gilbert
2019-07-09  8:15   ` Stefan Hajnoczi
2019-07-09  9:31     ` Miklos Szeredi

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=5D1F08B6.8000900@huawei.com \
    --to=piaojun@huawei.com \
    --cc=stefanha@redhat.com \
    --cc=virtio-fs@redhat.com \
    /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.