All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Jan Kara <jack@suse.cz>,
	Richard Weinberger <richard.weinberger@gmail.com>,
	Christoph Hellwig <hch@infradead.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Dongsheng Yang <yangds.fnst@cn.fujitsu.com>,
	Richard Weinberger <richard@nod.at>,
	linux-mtd@lists.infradead.org, kernel@pengutronix.de
Subject: Re: UBIFS quota support
Date: Mon, 28 Jan 2019 00:09:38 -0800	[thread overview]
Message-ID: <20190128080938.GA1076@infradead.org> (raw)
In-Reply-To: <20190125092156.ck77sdqainmmewuz@pengutronix.de>

FYI, the main reason (well, besides history) that XFS uses its own
quota code is so that it can have full integration with the transaction
subsystem and the on-disk data structures.

While it is going to be a lot more code you might want to look into
implementing quota accounting in ubifs itself and only use the
standard interfaces to report and adminstrate the quota values.

That way you might not even have to maintain a separate quota file and
could instead maintain usage statistics in the btree nodes, and only
summarize them in memory, possibly with a periodical full state dump.

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>,
	Jan Kara <jack@suse.cz>,
	Richard Weinberger <richard.weinberger@gmail.com>,
	Richard Weinberger <richard@nod.at>,
	Christoph Hellwig <hch@infradead.org>,
	linux-mtd@lists.infradead.org, kernel@pengutronix.de,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: UBIFS quota support
Date: Mon, 28 Jan 2019 00:09:38 -0800	[thread overview]
Message-ID: <20190128080938.GA1076@infradead.org> (raw)
In-Reply-To: <20190125092156.ck77sdqainmmewuz@pengutronix.de>

FYI, the main reason (well, besides history) that XFS uses its own
quota code is so that it can have full integration with the transaction
subsystem and the on-disk data structures.

While it is going to be a lot more code you might want to look into
implementing quota accounting in ubifs itself and only use the
standard interfaces to report and adminstrate the quota values.

That way you might not even have to maintain a separate quota file and
could instead maintain usage statistics in the btree nodes, and only
summarize them in memory, possibly with a periodical full state dump.

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2019-01-28  8:09 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 11:44 UBIFS quota support Sascha Hauer
2019-01-10 11:44 ` Sascha Hauer
2019-01-22 23:07 ` Richard Weinberger
2019-01-22 23:07   ` Richard Weinberger
2019-01-23  9:43   ` Sascha Hauer
2019-01-23  9:43     ` Sascha Hauer
2019-01-23  9:46     ` Richard Weinberger
2019-01-23  9:46       ` Richard Weinberger
2019-01-23  9:55       ` Sascha Hauer
2019-01-23  9:55         ` Sascha Hauer
2019-01-23 10:47         ` Richard Weinberger
2019-01-23 10:47           ` Richard Weinberger
2019-01-23 15:47   ` Jan Kara
2019-01-23 15:47     ` Jan Kara
2019-01-25  9:21     ` Sascha Hauer
2019-01-25  9:21       ` Sascha Hauer
2019-01-28  8:09       ` Christoph Hellwig [this message]
2019-01-28  8:09         ` Christoph Hellwig
2019-01-30 12:45       ` Jan Kara
2019-01-30 12:45         ` Jan Kara
2019-01-31  7:37         ` Sascha Hauer
2019-01-31  7:37           ` Sascha Hauer

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=20190128080938.GA1076@infradead.org \
    --to=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=kernel@pengutronix.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard.weinberger@gmail.com \
    --cc=richard@nod.at \
    --cc=s.hauer@pengutronix.de \
    --cc=yangds.fnst@cn.fujitsu.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
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.