All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Harry G. Coin" <hgcoin@gmail.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: virtio-fs@redhat.com
Subject: Re: [Virtio-fs] Can libvirt parse virtiofsd -o writeback?
Date: Fri, 18 Sep 2020 14:06:11 -0500	[thread overview]
Message-ID: <1b3d3efe-b3b8-1711-4993-956e88da9b7d@gmail.com> (raw)
In-Reply-To: <20200918185548.GS2816@work-vm>


On 9/18/20 1:55 PM, Dr. David Alan Gilbert wrote:
> * Harry G. Coin (hgcoin@gmail.com) wrote:
>> Is there any libvirt xml parser rev that knows about how to set
>> virtiofsd -o writeback?
> I don't think so ; the docs say:
> https://libvirt.org/formatdomain.html#filesystems
> says:
>
>  binary
>
>     The optional binary element can tune the options for virtiofsd. All
>     of the following attributes and elements are optional. The attribute
>     path can be used to override the path to the daemon. Attribute xattr
>     enables the use of filesystem extended attributes. Caching can be
>     tuned via the cache element, possible mode values being none and
>     always. Locking can be controlled via the lock element - attributes
>     posix and flock both accepting values on or off. ( Since 6.2.0 )
>
>
> Hmm, I've never tried the -o writeback; have you found it beneficial?
>
> Dave

Jury is still out.  Writeback without dax (which is unavailable outside
the high-interest bubble) subjectively seems to help a bit.  I have
managed to get a kernel boot going with generic environments, calls for
some hacking of initramfs, and most of the instructions about kernel
command line content is wrong on the info page.

Here's how folks can try writeback without having to cook up a dev
environment:

The paths below are for debian/ubuntu style distos, the rhel/centos
paths differ a bit.   I don't have the SELinux equivalent to the
apparmor glue.

Libvirt xml:

...

<filesystem type="mount" accessmode="passthrough">
  <driver type="virtiofs" queue="1024"/>
  <binary path="/usr/local/sbin/custom_virtiofsd" xattr="on">
    <lock posix="off" flock="on"/>
  </binary>

cat >  /usr/local/sbin/custom_virtiofsd
#!/bin/bash
#Provide a way to add arguments libvirt doesn't know about.
set -o allexport
/usr/lib/qemu/virtiofsd $@ -o writeback

and

cat > /etc/apparmor.d/local/usr.sbin.libvirtd
/usr/local/sbin/custom_virtiofsd rux,


>
>> Thanks
>>
>> Harry Coin
>>
>>
>> _______________________________________________
>> Virtio-fs mailing list
>> Virtio-fs@redhat.com
>> https://www.redhat.com/mailman/listinfo/virtio-fs



      reply	other threads:[~2020-09-18 19:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17 17:40 [Virtio-fs] Can libvirt parse virtiofsd -o writeback? Harry G. Coin
2020-09-18 18:55 ` Dr. David Alan Gilbert
2020-09-18 19:06   ` Harry G. Coin [this message]

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=1b3d3efe-b3b8-1711-4993-956e88da9b7d@gmail.com \
    --to=hgcoin@gmail.com \
    --cc=dgilbert@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.