From: Beata Michalska <b.k.m.devel@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: Christoph Hellwig <hch@infradead.org>,
Kyungmin Park <kmpark@infradead.org>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Hugh Dickins <hughd@google.com>, linux-mm <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Linux Filesystem Mailing List <linux-fsdevel@vger.kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [RFC] shmem: Add eventfd notification on utlilization level
Date: Tue, 10 Mar 2015 16:25:12 +0100 [thread overview]
Message-ID: <54FF0CD8.10709@gmail.com> (raw)
In-Reply-To: <20150310142237.GA2095@quack.suse.cz>
On 03/10/2015 03:22 PM, Jan Kara wrote:
> On Tue 10-03-15 06:03:23, Christoph Hellwig wrote:
>> On Tue, Mar 10, 2015 at 10:51:41AM +0900, Kyungmin Park wrote:
>>> Any updates?
>> Please just add disk quota support to tmpfs so thast the standard quota
>> netlink notifications can be used.
> If I understand the problem at hand, they are really interested in
> notification when running out of free space. Using quota for that doesn't
> seem ideal since that tracks used space per user, not free space on fs as a
> whole.
>
> But if I remember right there were discussions about ENOSPC notification
> from filesystem for thin provisioning usecases. It would be good to make
> this consistent with those but I'm not sure if it went anywhere.
>
> Honza
The ideal case here, would be to get the notification, despite the type
of the actual filesystem, whenever the amount of free space drops below
a certain level. Quota doesn't seem to be the right approach here.
BR
Beata Michalska
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-03-10 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 14:50 Krzysztof Kozlowski
2015-02-11 14:50 ` Krzysztof Kozlowski
2015-03-10 1:51 ` Kyungmin Park
2015-03-10 13:03 ` Christoph Hellwig
2015-03-10 14:22 ` Jan Kara
2015-03-10 15:25 ` Beata Michalska [this message]
2015-03-10 16:13 ` Lukáš Czerner
2015-03-11 4:35 ` Kyungmin Park
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=54FF0CD8.10709@gmail.com \
--to=b.k.m.devel@gmail.com \
--cc=b.zolnierkie@samsung.com \
--cc=hch@infradead.org \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=k.kozlowski@samsung.com \
--cc=kmpark@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=viro@zeniv.linux.org.uk \
/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