linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Artem Blagodarenko <artem.blagodarenko@gmail.com>
To: linux-ext4@vger.kernel.org
Cc: adilger.kernel@dilger.ca
Subject: [PATCH v3 0/3] 64 bit inode counter support
Date: Thu, 30 Nov 2017 18:17:50 +0300	[thread overview]
Message-ID: <20171130151753.24986-1-artem.blagodarenko@gmail.com> (raw)

With current hardware clusters faced with the trouble of
creating enough inodes on partitions. Lustre has 0-size
files to store some information about files. Current
MDS disk sizes allow to store large amount of such files, but
EXT4 limits this number to ~4 billions.

Lustre FS has features like DNE to distribute metadata over many targets
(disks), but disks are used not effectively. It would be great to have
ability to store more then ~4 billions inodes on one EXT4 file system.

This patches add 1) dirdata feature, that allow to store additional
data in direntry 2)  code that uses dirdata to store high bits of 
64bit inode number.

This is third version of the patch set. Changes since v2:
* added patch "Removes static definition of dx_root struct"
* __le32 used for on-disk data structures
* used __u8 type not char
* macroses __EXT4_DIR_REC_LEN and EXT4_DIR_REC_LEN renamed
* added structures to address dirent fields
* removed BUG_ON() execution
* no need to add s_usr_quota_inum_hi and s_grp_quota_inum_hi
* checksum using high part of inode
* fixed bug in size check code

Andreas Dilger (1):
  ext4: dirdata feature

Artem Blagodarenko (1):
  ext4: Add 64-bit inode number support

Yang Sheng (1):
  ext4: Removes static definition of dx_root struct

 fs/ext4/dir.c    |  21 ++--
 fs/ext4/ext4.h   | 184 +++++++++++++++++++++++++++++++----
 fs/ext4/ialloc.c |  19 ++--
 fs/ext4/inline.c |  18 ++--
 fs/ext4/inode.c  |   5 +
 fs/ext4/namei.c  | 289 ++++++++++++++++++++++++++++++++++++++-----------------
 fs/ext4/resize.c |   8 +-
 fs/ext4/super.c  |  17 +++-
 8 files changed, 423 insertions(+), 138 deletions(-)

-- 
2.13.6 (Apple Git-96)

             reply	other threads:[~2017-11-30 15:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30 15:17 Artem Blagodarenko [this message]
2017-11-30 15:17 ` [PATCH v3 1/3] ext4: Removes static definition of dx_root struct Artem Blagodarenko
2017-11-30 22:17   ` Andreas Dilger
2017-11-30 15:17 ` [PATCH v3 2/3] ext4: dirdata feature Artem Blagodarenko
2017-12-05  1:02   ` Andreas Dilger
2017-11-30 15:17 ` [PATCH v3 3/3] ext4: Add 64-bit inode number support Artem Blagodarenko
2017-12-05 21:26   ` Andreas Dilger

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=20171130151753.24986-1-artem.blagodarenko@gmail.com \
    --to=artem.blagodarenko@gmail.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=linux-ext4@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 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).