From: Jens Axboe <axboe@kernel.dk>
To: linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org
Cc: adilger@dilger.ca, Jens Axboe <axboe@kernel.dk>
Subject: [PATCH 03/10] fs: add support for an inode to carry stream related data
Date: Tue, 13 Jun 2017 22:01:52 -0600 [thread overview]
Message-ID: <1497412919-19400-4-git-send-email-axboe@kernel.dk> (raw)
In-Reply-To: <1497412919-19400-1-git-send-email-axboe@kernel.dk>
No functional changes in this patch, just in preparation for
allowing applications to pass in hints about data life times
for writes.
Pack the i_stream field into a 2-byte hole, so we don't grow
the size of the inode.
Reviewed-by: Andreas Dilger <adilger@dilger.ca>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
---
fs/inode.c | 1 +
include/linux/fs.h | 9 +++++++++
2 files changed, 10 insertions(+)
diff --git a/fs/inode.c b/fs/inode.c
index db5914783a71..5717cb378fda 100644
--- a/fs/inode.c
+++ b/fs/inode.c
@@ -149,6 +149,7 @@ int inode_init_always(struct super_block *sb, struct inode *inode)
inode->i_blocks = 0;
inode->i_bytes = 0;
inode->i_generation = 0;
+ inode->i_stream = 0;
inode->i_pipe = NULL;
inode->i_bdev = NULL;
inode->i_cdev = NULL;
diff --git a/include/linux/fs.h b/include/linux/fs.h
index 803e5a9b2654..771e172d23d7 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -591,6 +591,7 @@ struct inode {
struct timespec i_ctime;
spinlock_t i_lock; /* i_blocks, i_bytes, maybe i_size */
unsigned short i_bytes;
+ unsigned short i_stream;
unsigned int i_blkbits;
blkcnt_t i_blocks;
@@ -655,6 +656,14 @@ struct inode {
void *i_private; /* fs or device private pointer */
};
+static inline unsigned int inode_streamid(struct inode *inode)
+{
+ if (inode)
+ return inode->i_stream;
+
+ return 0;
+}
+
static inline unsigned int i_blocksize(const struct inode *node)
{
return (1 << node->i_blkbits);
--
2.7.4
next prev parent reply other threads:[~2017-06-14 4:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 4:01 [PATCHSET v2] Add support for write life time hints Jens Axboe
2017-06-14 4:01 ` [PATCH 01/10] block: add support for carrying stream information in a bio Jens Axboe
2017-06-14 4:01 ` [PATCH 02/10] blk-mq: expose stream write stats through debugfs Jens Axboe
2017-06-14 4:07 ` Andreas Dilger
2017-06-14 4:01 ` Jens Axboe [this message]
2017-06-14 4:01 ` [PATCH 04/10] fs: add support for allowing applications to pass in write life time hints Jens Axboe
2017-06-14 4:06 ` Andreas Dilger
2017-06-14 4:01 ` [PATCH 05/10] fs: add O_DIRECT support for sending down bio stream information Jens Axboe
2017-06-14 4:01 ` [PATCH 06/10] fs: add support for buffered writeback to pass down " Jens Axboe
2017-06-14 4:01 ` [PATCH 07/10] ext4: add support for passing in stream information for buffered writes Jens Axboe
2017-06-14 4:01 ` [PATCH 08/10] xfs: " Jens Axboe
2017-06-14 4:01 ` [PATCH 09/10] btrfs: " Jens Axboe
2017-06-14 4:01 ` [PATCH 10/10] nvme: add support for streams and directives Jens Axboe
2017-06-14 4:10 ` Andreas Dilger
2017-06-14 15:45 ` [PATCHSET v2] Add support for write life time hints Martin K. Petersen
2017-06-14 15:53 ` Jens Axboe
2017-06-14 16:00 ` Martin K. Petersen
2017-06-14 16:03 ` Jens Axboe
2017-06-14 16:01 ` Christoph Hellwig
2017-06-14 16:02 ` Jens Axboe
2017-06-14 16:04 ` Martin K. Petersen
2017-06-14 16:26 ` Jens Axboe
2017-06-14 17:22 ` Jens Axboe
2017-06-14 23:39 ` Andreas Dilger
2017-06-15 3:26 ` Jens Axboe
2017-06-15 3:53 ` Andreas Dilger
2017-06-15 3:57 ` Jens Axboe
2017-06-15 4:38 ` Jens Axboe
2017-06-16 13:58 ` Christoph Hellwig
2017-06-16 14:40 ` Jens Axboe
2017-06-16 15:52 ` Christoph Hellwig
2017-06-16 15:55 ` Jens Axboe
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=1497412919-19400-4-git-send-email-axboe@kernel.dk \
--to=axboe@kernel.dk \
--cc=adilger@dilger.ca \
--cc=linux-block@vger.kernel.org \
--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 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).