($INBOX_DIR/description missing)
 help / color / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	overlayfs <linux-unionfs@vger.kernel.org>,
	Giuseppe Scrivano <gscrivan@redhat.com>,
	Daniel J Walsh <dwalsh@redhat.com>,
	Steven Whitehouse <swhiteho@redhat.com>,
	pmatilai@redhat.com, Eric Sandeen <sandeen@redhat.com>
Subject: Re: [PATCH v4] overlayfs: Provide mount options sync=off/fs to skip sync
Date: Mon, 20 Jul 2020 20:47:14 +0300
Message-ID: <CAOQ4uxjijzhtk4V=4VnyTbh9xKHtPEUQsOOPTs36yi93Kp3ArQ@mail.gmail.com> (raw)
In-Reply-To: <20200720161618.GD502563@redhat.com>

> >
> > Naming: I'm not at all convinced by any name having "sync" in it.  I
> > think "sync=no" is about the implementation, not the functionality,
> > and so it's confusing. The functionality is better described by
> > "volatile" or "temporary".   But I can live with sync=... if voted
> > down.
>
> I am fine with the name "volatile/temporary" for sync=off.
>
> Amir, WDYT?

If we knew we were going to stop here, I wouldn't mind "volatile".
I too like the fact that the user config means something functional.
But if we are considering to expand it later to sync=fs and maybe
sync=writeback, then it is going to be quite hard to come by with
equally meaningful names and the "sync=" modes would end up
being less confusing IMO.

So I cast my vote for "sync=off".
We could also make "volatile" an alias to "sync=off" if it makes
anyone happier.

Thanks,
Amir.

  reply index

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06 16:12 Vivek Goyal
2020-07-06 17:16 ` Amir Goldstein
2020-07-20 12:57 ` Miklos Szeredi
2020-07-20 16:16   ` Vivek Goyal
2020-07-20 17:47     ` Amir Goldstein [this message]
2020-07-21 13:15     ` Miklos Szeredi
2020-07-21 13:44       ` Amir Goldstein
2020-07-21 13:51       ` Vivek Goyal

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='CAOQ4uxjijzhtk4V=4VnyTbh9xKHtPEUQsOOPTs36yi93Kp3ArQ@mail.gmail.com' \
    --to=amir73il@gmail.com \
    --cc=dwalsh@redhat.com \
    --cc=gscrivan@redhat.com \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=pmatilai@redhat.com \
    --cc=sandeen@redhat.com \
    --cc=swhiteho@redhat.com \
    --cc=vgoyal@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

($INBOX_DIR/description missing)

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-unionfs/0 linux-unionfs/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-unionfs linux-unionfs/ https://lore.kernel.org/linux-unionfs \
		linux-unionfs@vger.kernel.org
	public-inbox-index linux-unionfs

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-unionfs


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git