From: Amir Goldstein <amir73il@gmail.com>
To: cgxu <cgxu519@mykernel.net>
Cc: Jan Kara <jack@suse.cz>, Miklos Szeredi <miklos@szeredi.hu>,
overlayfs <linux-unionfs@vger.kernel.org>,
Sargun Dhillon <sargun@sargun.me>
Subject: Re: [PATCH v12] ovl: improve syncfs efficiency
Date: Tue, 26 May 2020 11:25:47 +0300 [thread overview]
Message-ID: <CAOQ4uxig6SXJnMKPbA95_JkWnWLU_tY_yKn9vW4mvGqw=qKuzg@mail.gmail.com> (raw)
In-Reply-To: <6bce615e-b8ef-e63f-3829-e2b785a02f5d@mykernel.net>
> >> In high density container environment, especially for temporary jobs,
> >> this is quite unwilling behavior. Should we provide an option to
> >> mitigate this effect for containers which don't care about dirty data?
> >>
> >
> > This is not the first time this sort of suggestion has been made:
> > https://lore.kernel.org/linux-unionfs/4bc73729-5d85-36b7-0768-ae5952ae05e9@mykernel.net/T/#md5fc5d51852016da7e042f5d9e5ef7a6d21ea822
>
> The link above seems just my mail thread in mail list.
>
Heh sorry. Wrong link. Here it is:
https://lore.kernel.org/linux-unionfs/CAMp4zn9NsrdByVzWbThBd7Y0DsufJnqp=LdbDscbtyZx82E0Ug@mail.gmail.com/
Sargun, do you have anything to contribute to this discussion from
your experience?
Are you using Ephemeral containers?
Thanks,
Amir.
next prev parent reply other threads:[~2020-05-26 8:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 9:53 [PATCH v12] ovl: improve syncfs efficiency Chengguang Xu
2020-05-20 1:01 ` cgxu
2020-05-20 7:24 ` Amir Goldstein
2020-05-22 9:31 ` Miklos Szeredi
2020-05-22 13:44 ` Vivek Goyal
2020-05-22 14:40 ` Giuseppe Scrivano
2020-05-26 7:50 ` cgxu
2020-05-26 8:25 ` Amir Goldstein [this message]
2020-08-31 14:22 ` cgxu
2020-08-31 14:58 ` 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='CAOQ4uxig6SXJnMKPbA95_JkWnWLU_tY_yKn9vW4mvGqw=qKuzg@mail.gmail.com' \
--to=amir73il@gmail.com \
--cc=cgxu519@mykernel.net \
--cc=jack@suse.cz \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=sargun@sargun.me \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).