From: Viacheslav Dubeyko <slava@dubeyko.com>
To: Goldwyn Rodrigues <rgoldwyn@suse.de>
Cc: linux-fsdevel@vger.kernel.org, Goldwyn Rodrigues <rgoldwyn@suse.com>
Subject: Re: [PoC 0/7] Kobjectify filesystem
Date: Fri, 29 Apr 2016 10:32:59 -0700 [thread overview]
Message-ID: <1461951179.2619.5.camel@slavad-ubuntu-14.04> (raw)
In-Reply-To: <1461895282-4941-1-git-send-email-rgoldwyn@suse.de>
Hi Goldwyn,
On Thu, 2016-04-28 at 21:01 -0500, Goldwyn Rodrigues wrote:
> From: Goldwyn Rodrigues <rgoldwyn@suse.com>
>
> This is an effort to represent fs structures in terms of kobjects.
>
> The primary goal of this was to provide a mechanism for the filesystems
> to provide feedback to userspace but grew more than that.
> In case of errors users may fix errors and could schedule a
> complete filesystem check at a later point of time.
> ENOSPC errors could be automated to delete temporary files
> etc.
>
> As a implementation example, I have changed ocfs2 to support the change,
> though it is not completely feasible change because of the way ksets are
> represented in kset, but it delivers the idea.
>
> Taking this forward may reduce the house-keeping tasks such as searching,
> list handling and locking. One example shown here is the super_block
> destruction using kobjects. Since most filesystems do represent their
> structures in sysfs, this would consolidate individual representations
> under the filesystem, hopefully reducing code.
>
> Let me know what you think about the idea.
>
You can register any attributes in sysfs. So, what do you suggest
finally? What common scheme for all file systems do you suggest to use?
Suppose, I didn't catch the idea. Did you invent sysfs itself? Could you
describe your vision more clearly? The idea looks obscure right now,
from my point of view.
Thanks,
Vyacheslav Dubeyko.
next prev parent reply other threads:[~2016-04-29 17:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 2:01 [PoC 0/7] Kobjectify filesystem Goldwyn Rodrigues
2016-04-29 2:01 ` [PoC 1/7] Add kset to file_system_type Goldwyn Rodrigues
2016-04-29 2:01 ` [PoC 2/7] Add kobject to super_block Goldwyn Rodrigues
2016-04-29 2:26 ` Al Viro
2016-04-29 19:09 ` Goldwyn Rodrigues
2016-04-29 2:01 ` [PoC 3/7] Create sysfs files under sb Goldwyn Rodrigues
2016-04-29 2:01 ` [PoC 4/7] Report file system events Goldwyn Rodrigues
2016-04-29 2:01 ` [PoC 5/7] ocfs2: Use the sb's kset Goldwyn Rodrigues
2016-04-29 2:01 ` [PoC 6/7] ocfs2: create filecheck files Goldwyn Rodrigues
2016-04-29 2:01 ` [PoC 7/7] ocfs2: report inode errors to userspace Goldwyn Rodrigues
2016-04-29 17:32 ` Viacheslav Dubeyko [this message]
2016-04-29 18:28 ` [PoC 0/7] Kobjectify filesystem Goldwyn Rodrigues
2016-04-29 20:16 ` Viacheslav Dubeyko
2016-04-29 22:09 ` Goldwyn Rodrigues
2016-04-29 22:31 ` Al Viro
2016-04-29 22:45 ` Goldwyn Rodrigues
2016-05-04 22:20 ` Dave Chinner
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=1461951179.2619.5.camel@slavad-ubuntu-14.04 \
--to=slava@dubeyko.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rgoldwyn@suse.com \
--cc=rgoldwyn@suse.de \
/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).