All of lore.kernel.org
 help / color / mirror / Atom feed
From: Beata Michalska <b.michalska@samsung.com>
To: tytso@mit.edu, adilger.kernel@dilger.ca
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	kyungmin.park@samsung.com
Subject: [RFC] ext4: Add pollable sysfs entry for block threshold events
Date: Wed, 11 Mar 2015 11:16:32 +0100	[thread overview]
Message-ID: <1426068993-1051-1-git-send-email-b.michalska@samsung.com> (raw)

Hi All,

There has been a request to provide a notification whenever
the amount of free space drops below a certain level.
This level, preferably, could be adjusted based on the actual
space usage, so that appropraite actions can be undertaken
for different levels being reached. The idea here is to expose
a pollabe sysfs entry through which the threshold can be spcified,
in a form of a number of used logical blocks. Then, the process might
wait for a notification, through the very same sysfs entry, instead of
periodically calling statfs - as the concept introduced, is to
resemble the very last with hopefully, minimum overhead. When
the process wakes-up it might decide to increase the threshold
and once again wait for the notification.

BR
Beata Michalska
----
Beate Michalska (1):
  ext4: Add pollable sysfs entry for block threshold events

 fs/ext4/balloc.c  |   17 ++++-------------
 fs/ext4/ext4.h    |   12 ++++++++++++
 fs/ext4/ialloc.c  |    5 +----
 fs/ext4/inode.c   |    2 +-
 fs/ext4/mballoc.c |   14 ++++----------
 fs/ext4/resize.c  |    3 ++-
 fs/ext4/super.c   |   52 ++++++++++++++++++++++++++++++++++++++++++++++++++--
 7 files changed, 74 insertions(+), 31 deletions(-)

-- 
1.7.9.5


             reply	other threads:[~2015-03-11 10:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 10:16 Beata Michalska [this message]
2015-03-11 10:16 ` [RFC] ext4: Add pollable sysfs entry for block threshold events Beata Michalska
2015-03-11 14:12   ` Lukáš Czerner
2015-03-11 16:45     ` Beata Michalska
2015-03-11 17:49       ` Lukáš Czerner
2015-03-12  9:06         ` Beata Michalska
2015-03-13 15:05     ` Theodore Ts'o

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=1426068993-1051-1-git-send-email-b.michalska@samsung.com \
    --to=b.michalska@samsung.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.