All of lore.kernel.org
 help / color / mirror / Atom feed
From: cem@kernel.org
To: linux-fsdevel@vger.kernel.org
Cc: hughd@google.com, brauner@kernel.org, jack@suse.cz
Subject: [RFC PATCH 0/3] tmpfs: Add tmpfs project quota support
Date: Mon, 25 Sep 2023 15:00:25 +0200	[thread overview]
Message-ID: <20230925130028.1244740-1-cem@kernel.org> (raw)

From: Carlos Maiolino <cem@kernel.org>

Hi,

this is my first implementation attempt of project quotas on tmpfs, this is not
complete yet, it should still have statfs implementation and default block/inode
limits mount options for prjquota, other than that this series already make
prjquotas functional for tmpfs.
I'm sending this on early stage so maybe Jan, Hugh and Christian could comment on it
as they were in the loop during quota implementation for tmpfs. So maybe you
guys could take a look on it and give me your PoV?

Thanks

Carlos Maiolino (3):
  tmpfs: add project ID support
  tmpfs: Add project quota mount option
  tmpfs: Add project quota interface support for get/set attr

 include/linux/shmem_fs.h | 13 ++++++----
 mm/shmem.c               | 52 ++++++++++++++++++++++++++++++++++++----
 mm/shmem_quota.c         | 10 ++++++++
 3 files changed, 66 insertions(+), 9 deletions(-)

Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
-- 
2.39.2


             reply	other threads:[~2023-09-25 13:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-25 13:00 cem [this message]
2023-09-25 13:00 ` [PATCH 1/3] tmpfs: add project ID support cem
2023-10-03 11:23   ` Jan Kara
2023-09-25 13:00 ` [PATCH 2/3] tmpfs: Add project quota mount option cem
2023-09-25 13:00 ` [PATCH 3/3] tmpfs: Add project quota interface support for get/set attr cem
2023-09-26 20:28   ` Andreas Dilger
2023-09-27  1:09     ` Dave Chinner
2023-09-27 12:48     ` Carlos Maiolino
2023-09-26 21:35   ` kernel test robot
2023-10-02  8:41   ` kernel test robot

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=20230925130028.1244740-1-cem@kernel.org \
    --to=cem@kernel.org \
    --cc=brauner@kernel.org \
    --cc=hughd@google.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    /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.