On Oct 1, 2014, at 1:31 PM, Jan Kara wrote:
> There are parts of struct inode which are used only by a few filesystems
> (e.g. i_dquot pointers, i_mapping->private_list, ...). Thus all the
> other filesystems are just wasting memory with these fields. On the
> other hand it isn't simple to just mo
All filesystems using VFS quotas are now converted to use their private
i_dquot fields. Remove the i_dquot field from generic inode structure.
Signed-off-by: Jan Kara
---
fs/inode.c | 3 ---
fs/super.c | 10 --
include/linux/fs.h | 3 ---
3 files changed, 16 deletions(-
CC: Dave Kleikamp
CC: jfs-discuss...@lists.sourceforge.net
Signed-off-by: Jan Kara
---
fs/jfs/jfs_incore.h | 3 +++
fs/jfs/super.c | 13 +
2 files changed, 16 insertions(+)
diff --git a/fs/jfs/jfs_incore.h b/fs/jfs/jfs_incore.h
index cf47f09e8ac8..fa7e795bd8ae 100644
--- a/fs/
CC: linux-e...@vger.kernel.org
Signed-off-by: Jan Kara
---
fs/ext3/ext3.h | 4
fs/ext3/super.c | 13 +
2 files changed, 17 insertions(+)
diff --git a/fs/ext3/ext3.h b/fs/ext3/ext3.h
index e85ff15a060e..04f30a1f96cb 100644
--- a/fs/ext3/ext3.h
+++ b/fs/ext3/ext3.h
@@ -613,6 +61
i_dquot is a first candidate for using optional inode fields since it is
used by relatively few filesystems (ext?, ocfs2, jfs, reiserfs). We
cannot just pass quota pointers from filesystems to quota functions
because during quotaon and quotaoff we have to traverse list of all
inodes and manipulate
CC: linux-e...@vger.kernel.org
CC: "Theodore Ts'o"
Signed-off-by: Jan Kara
---
fs/ext4/ext4.h | 4
fs/ext4/super.c | 10 ++
2 files changed, 14 insertions(+)
diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
index b0c225cdb52c..571a9f409e94 100644
--- a/fs/ext4/ext4.h
+++ b/fs/ext4/ex
We support user and group quotas. Tell vfs about it.
CC: Steven Whitehouse
CC: cluster-devel@redhat.com
Signed-off-by: Jan Kara
---
fs/gfs2/ops_fstype.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/gfs2/ops_fstype.c b/fs/gfs2/ops_fstype.c
index d3eae244076e..3032e6d069b5 100644
--- a/
Currently all filesystems supporting VFS quota support user and group
quotas. With introduction of project quotas this is going to change so
make sure filesystem isn't called for quota type it doesn't support by
introduction of a bitmask determining which quota types each filesystem
supports.
Sign
CC: reiserfs-de...@vger.kernel.org
CC: Jeff Mahoney
Signed-off-by: Jan Kara
---
fs/reiserfs/reiserfs.h | 4
fs/reiserfs/super.c| 13 +
2 files changed, 17 insertions(+)
diff --git a/fs/reiserfs/reiserfs.h b/fs/reiserfs/reiserfs.h
index 735c2c2b4536..197e59cbeb1c 100644
---
There are parts of struct inode which are used only by a few filesystems
(e.g. i_dquot pointers, i_mapping->private_list, ...). Thus all the
other filesystems are just wasting memory with these fields. On the
other hand it isn't simple to just move these fields to filesystem
specific part of inode
We support user, group, and project quotas. Tell VFS about it.
CC: x...@oss.sgi.com
CC: Dave Chinner
Signed-off-by: Jan Kara
---
fs/xfs/xfs_super.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/xfs/xfs_super.c b/fs/xfs/xfs_super.c
index b194652033cd..b32e998e8cbc 100644
--- a/fs/xfs/
CC: linux-e...@vger.kernel.org
Signed-off-by: Jan Kara
---
fs/ext2/ext2.h | 3 +++
fs/ext2/super.c | 13 +
2 files changed, 16 insertions(+)
diff --git a/fs/ext2/ext2.h b/fs/ext2/ext2.h
index d9a17d0b124d..e4279ead4a05 100644
--- a/fs/ext2/ext2.h
+++ b/fs/ext2/ext2.h
@@ -689,6 +689
Hello,
this patch set moves i_dquot array from struct inode into filesystem private
part of the inode. Thus filesystems which don't need it save 2 pointers in
their inodes (would be 3 after we add project quota support into generic
quota).
I have patches to move inode->i_data.private_list int
CC: Mark Fasheh
CC: Joel Becker
CC: ocfs2-de...@oss.oracle.com
Signed-off-by: Jan Kara
---
fs/ocfs2/inode.h | 4
fs/ocfs2/super.c | 12
2 files changed, 16 insertions(+)
diff --git a/fs/ocfs2/inode.h b/fs/ocfs2/inode.h
index a6c991c0fc98..aed65d3aff57 100644
--- a/fs/ocfs2/i
On Wed, Oct 01, 2014 at 01:21:41PM -0400, Bob Peterson wrote:
> Hi,
>
> This patch adds a new lock flag, DLM_LKF_NOLOOKUP, which instructs DLM
> to refrain from sending lookup requests in cases where the lock library
> node is not the current node. This is similar to the DLM_LKF_NOQUEUE
> flag, ex
Hi,
On 01/10/14 18:21, Bob Peterson wrote:
Hi,
This patch adds a new lock flag, DLM_LKF_NOLOOKUP, which instructs DLM
to refrain from sending lookup requests in cases where the lock library
node is not the current node. This is similar to the DLM_LKF_NOQUEUE
flag, except it fails locks that wou
Hi,
This patch adds a new lock flag, DLM_LKF_NOLOOKUP, which instructs DLM
to refrain from sending lookup requests in cases where the lock library
node is not the current node. This is similar to the DLM_LKF_NOQUEUE
flag, except it fails locks that would require a lookup, with -EAGAIN.
This is no
Hi,
On 29/09/14 13:52, Bob Peterson wrote:
Hi,
This patch fixes a regression in the patch "GFS2: Remember directory
insert point", commit 2b47dad866d04f14c328f888ba5406057b8c7d33.
The problem had to do with the rename function: The function found
space for the new dirent, and remembered that lo
18 matches
Mail list logo
