From: Chris Mason <chris.mason@oracle.com>
To: chris.mason@oracle.com
Cc: akpm@linux-foundation.org, torvalds@linux-foundation.org,
linux-fsdevel@vger.kernel.org
Subject: [PATCH 27/35] Btrfs in-memory inode.h
Date: Wed, 7 Jan 2009 22:57:17 -0500 [thread overview]
Message-ID: <1231387045-27838-28-git-send-email-chris.mason@oracle.com> (raw)
In-Reply-To: <1231387045-27838-1-git-send-email-chris.mason@oracle.com>
This defines the btrfs in-memory inode.
Signed-off-by: Chris Mason <chris.mason@oracle.com>
diff --git a/fs/btrfs/btrfs_inode.h b/fs/btrfs/btrfs_inode.h
new file mode 100644
index 0000000..a8c9693
--- /dev/null
+++ b/fs/btrfs/btrfs_inode.h
@@ -0,0 +1,131 @@
+/*
+ * Copyright (C) 2007 Oracle. All rights reserved.
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public
+ * License v2 as published by the Free Software Foundation.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ * General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public
+ * License along with this program; if not, write to the
+ * Free Software Foundation, Inc., 59 Temple Place - Suite 330,
+ * Boston, MA 021110-1307, USA.
+ */
+
+#ifndef __BTRFS_I__
+#define __BTRFS_I__
+
+#include "extent_map.h"
+#include "extent_io.h"
+#include "ordered-data.h"
+
+/* in memory btrfs inode */
+struct btrfs_inode {
+ /* which subvolume this inode belongs to */
+ struct btrfs_root *root;
+
+ /* key used to find this inode on disk. This is used by the code
+ * to read in roots of subvolumes
+ */
+ struct btrfs_key location;
+
+ /* the extent_tree has caches of all the extent mappings to disk */
+ struct extent_map_tree extent_tree;
+
+ /* the io_tree does range state (DIRTY, LOCKED etc) */
+ struct extent_io_tree io_tree;
+
+ /* special utility tree used to record which mirrors have already been
+ * tried when checksums fail for a given block
+ */
+ struct extent_io_tree io_failure_tree;
+
+ /* held while inesrting or deleting extents from files */
+ struct mutex extent_mutex;
+
+ /* held while logging the inode in tree-log.c */
+ struct mutex log_mutex;
+
+ /* used to order data wrt metadata */
+ struct btrfs_ordered_inode_tree ordered_tree;
+
+ /* standard acl pointers */
+ struct posix_acl *i_acl;
+ struct posix_acl *i_default_acl;
+
+ /* for keeping track of orphaned inodes */
+ struct list_head i_orphan;
+
+ /* list of all the delalloc inodes in the FS. There are times we need
+ * to write all the delalloc pages to disk, and this list is used
+ * to walk them all.
+ */
+ struct list_head delalloc_inodes;
+
+ /* full 64 bit generation number, struct vfs_inode doesn't have a big
+ * enough field for this.
+ */
+ u64 generation;
+
+ /* sequence number for NFS changes */
+ u64 sequence;
+
+ /*
+ * transid of the trans_handle that last modified this inode
+ */
+ u64 last_trans;
+ /*
+ * transid that last logged this inode
+ */
+ u64 logged_trans;
+
+ /*
+ * trans that last made a change that should be fully fsync'd. This
+ * gets reset to zero each time the inode is logged
+ */
+ u64 log_dirty_trans;
+
+ /* total number of bytes pending delalloc, used by stat to calc the
+ * real block usage of the file
+ */
+ u64 delalloc_bytes;
+
+ /*
+ * the size of the file stored in the metadata on disk. data=ordered
+ * means the in-memory i_size might be larger than the size on disk
+ * because not all the blocks are written yet.
+ */
+ u64 disk_i_size;
+
+ /* flags field from the on disk inode */
+ u32 flags;
+
+ /*
+ * if this is a directory then index_cnt is the counter for the index
+ * number for new files that are created
+ */
+ u64 index_cnt;
+
+ /* the start of block group preferred for allocations. */
+ u64 block_group;
+
+ struct inode vfs_inode;
+};
+
+static inline struct btrfs_inode *BTRFS_I(struct inode *inode)
+{
+ return container_of(inode, struct btrfs_inode, vfs_inode);
+}
+
+static inline void btrfs_i_size_write(struct inode *inode, u64 size)
+{
+ inode->i_size = size;
+ BTRFS_I(inode)->disk_i_size = size;
+}
+
+
+#endif
--
1.6.0.2
next prev parent reply other threads:[~2009-01-08 3:58 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 3:56 [PATCH 00/35] Btrfs for review Chris Mason
2009-01-08 3:56 ` [PATCH 01/35] Btrfs xattr code Chris Mason
2009-01-13 4:59 ` Andrew Morton
2009-01-13 12:56 ` Josef Bacik
2009-01-13 14:37 ` Chris Mason
2009-01-08 3:56 ` [PATCH 02/35] Btrfs multi-device code Chris Mason
2009-01-13 6:23 ` Andrew Morton
2009-01-13 16:36 ` Chris Mason
2009-01-13 17:52 ` Andrew Morton
2009-01-13 17:58 ` Chris Mason
2009-01-30 15:09 ` Andy Whitcroft
2009-01-08 3:56 ` [PATCH 03/35] Btrfs tree logging (fsync optimizations) Chris Mason
2009-01-08 3:56 ` [PATCH 04/35] Btrfs transaction code Chris Mason
2009-01-08 3:56 ` [PATCH 05/35] Btrfs btree leaf reference cache Chris Mason
2009-01-08 3:56 ` [PATCH 06/35] Btrfs tree printk debugging Chris Mason
2009-01-08 3:56 ` [PATCH 07/35] Btrfs ordered data processing Chris Mason
2009-01-08 3:56 ` [PATCH 08/35] Btrfs btree locking helpers Chris Mason
2009-01-08 3:56 ` [PATCH 09/35] Btrfs zlib helpers Chris Mason
2009-01-08 3:57 ` [PATCH 10/35] Btrfs online btree defragging Chris Mason
2009-01-08 3:57 ` [PATCH 11/35] Btrfs sysfs routines Chris Mason
2009-01-08 3:57 ` [PATCH 12/35] Btrfs super operations Chris Mason
2009-01-08 3:57 ` [PATCH 13/35] Btrfs metadata access routines Chris Mason
2009-01-08 3:57 ` [PATCH 14/35] Btrfs tree of tree roots code Chris Mason
2009-01-08 3:57 ` [PATCH 15/35] Btrfs Orphan prevention Chris Mason
2009-01-08 3:57 ` [PATCH 16/35] Btrfs free inode allocation Chris Mason
2009-01-08 3:57 ` [PATCH 17/35] Btrfs inode item routines Chris Mason
2009-01-08 3:57 ` [PATCH 19/35] Btrfs directory name hashing Chris Mason
2009-01-08 3:57 ` [PATCH 20/35] Btrfs free space caching Chris Mason
2009-01-08 3:57 ` [PATCH 21/35] Btrfs file-item and checksumming routines Chris Mason
2009-01-08 3:57 ` [PATCH 22/35] Btrfs file write routines Chris Mason
2009-01-08 3:57 ` [PATCH 24/35] Btrfs directory item routines Chris Mason
2009-01-08 3:57 ` [PATCH 25/35] Btrfs main metadata header file Chris Mason
2009-01-08 3:57 ` Chris Mason [this message]
2009-01-08 3:57 ` [PATCH 28/35] Btrfs acl implementation Chris Mason
2009-01-08 3:57 ` [PATCH 29/35] Btrfs ioctl code Chris Mason
2009-01-15 18:29 ` Ryusuke Konishi
2009-01-15 20:17 ` Linus Torvalds
2009-01-15 20:28 ` Chris Mason
2009-01-15 20:44 ` Linus Torvalds
2009-01-15 20:49 ` Chris Mason
2009-01-16 17:23 ` Chris Mason
2009-01-17 4:16 ` Ryusuke Konishi
2009-01-08 3:57 ` [PATCH 30/35] Btrfs extent_map: per-file extent lookup cache Chris Mason
2009-01-08 3:57 ` [PATCH 32/35] Btrfs NFS exporting routines Chris Mason
2009-01-08 3:57 ` [PATCH 33/35] Btrfs metadata disk-io routines Chris Mason
2009-01-08 3:57 ` [PATCH 34/35] Btrfs compression routines Chris Mason
2009-01-08 3:57 ` [PATCH 35/35] Async thread routines Chris Mason
2009-01-08 16:01 ` [PATCH 18.1/35] Btrfs inode operations Chris Mason
2009-01-08 16:04 ` [PATCH 18.2/35] Btrfs inode extent_io hooks Chris Mason
2009-01-08 16:06 ` [PATCH 23.1/35] Btrfs extent allocation code Chris Mason
2009-01-08 16:07 ` [PATCH 23.2/35] Btrfs snapshot deletion Chris Mason
2009-01-08 16:08 ` [PATCH 23.3/35] Btrfs extent relocation Chris Mason
2009-01-08 16:10 ` [PATCH 26.1/35] Btrfs btree core Chris Mason
2009-01-08 16:11 ` [PATCH 26.2/35] Btrfs btree item routines Chris Mason
2009-01-08 16:12 ` [PATCH 31.1/35] Btrfs extent io operations Chris Mason
2009-01-08 16:13 ` [PATCH 31.2/35] Btrfs extent_buffer code Chris Mason
2009-01-09 2:28 ` [PATCH 00/35] Btrfs for review Andi Kleen
2009-01-09 21:13 ` Chris Mason
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=1231387045-27838-28-git-send-email-chris.mason@oracle.com \
--to=chris.mason@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).