All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: virtio-fs-list <virtio-fs@redhat.com>
Cc: Mrunal Patel <mpatel@redhat.com>, Miklos Szeredi <miklos@szeredi.hu>
Subject: [Virtio-fs] One virtiofs daemon per exported dir requirement
Date: Fri, 14 Feb 2020 14:27:05 -0500	[thread overview]
Message-ID: <20200214192705.GE18654@redhat.com> (raw)

Hi,

Dan Walsh and Mrunal mentioned that one virtiofsd daemon per exported
directory requirement sounds excessive. For container use case, they have
atleast 2-3 more directories they need to export (secrets and /etc/host). And
that means 3-4 virtiofsd running for each kata container. 

One option seems that bind mount all exports in one directory and export
that directory using one virtiofsd. I am aware of atleast one problem
with that configuraiton and that is possibility of inode number collision
if bind mounts are coming from different devices. Not sure how many
applications care though. Sergio is looking into solving this issue. It
might take a while though.

Any other thoughts?

Thanks
Vivek


             reply	other threads:[~2020-02-14 19:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14 19:27 Vivek Goyal [this message]
2020-02-14 19:41 ` [Virtio-fs] One virtiofs daemon per exported dir requirement Dr. David Alan Gilbert
2020-02-18 13:38   ` Stefan Hajnoczi
2020-02-18 18:28     ` Daniel Walsh
2020-02-18 18:29     ` Daniel Walsh
2020-02-18 18:32       ` Daniel Walsh
2020-02-18 18:58         ` Dr. David Alan Gilbert
2020-02-18 21:39           ` Daniel Walsh
2020-02-19 14:06             ` [Virtio-fs] Effect of nodev, noexec, nosuid mount options (Was: Re: One virtiofs daemon per exported dir requirement) Vivek Goyal
2020-02-21 15:38               ` Daniel Walsh
2020-02-19 15:24           ` [Virtio-fs] One virtiofs daemon per exported dir requirement Stefan Hajnoczi

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=20200214192705.GE18654@redhat.com \
    --to=vgoyal@redhat.com \
    --cc=miklos@szeredi.hu \
    --cc=mpatel@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.