From: Christoph Hellwig <hch@lst.de> To: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org, linux-block@vger.kernel.org Subject: [PATCH 11/12] block_dev: implement the F_IOINFO fcntl Date: Tue, 28 Feb 2017 06:57:36 -0800 [thread overview] Message-ID: <20170228145737.19016-12-hch@lst.de> (raw) In-Reply-To: <20170228145737.19016-1-hch@lst.de> Signed-off-by: Christoph Hellwig <hch@lst.de> --- fs/block_dev.c | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/fs/block_dev.c b/fs/block_dev.c index 4dd5c54cdefb..48a799964e1d 100644 --- a/fs/block_dev.c +++ b/fs/block_dev.c @@ -2116,6 +2116,26 @@ static long blkdev_fallocate(struct file *file, int mode, loff_t start, end >> PAGE_SHIFT); } +static int blkdev_ioinfo(struct file *file, struct fcntl_ioinfo *fio) +{ + struct block_device *bdev = I_BDEV(bdev_file_inode(file)); + struct request_queue *q = bdev_get_queue(bdev); + unsigned int atomic_sectors = queue_max_atomic_write_sectors(q); + + if (file->f_flags & O_DIRECT) { + fio->fio_alignment = bdev_logical_block_size(bdev); + + if ((file->f_flags & O_ATOMIC) && atomic_sectors) { + fio->fio_flags = FIO_FL_ATOMIC_OSYNC; + fio->fio_max_atomic = (atomic_sectors << 9); + if (fio->fio_alignment) + fio->fio_max_atomic &= ~(fio->fio_alignment - 1); + } + } + + return 0; +}; + const struct file_operations def_blk_fops = { .open = blkdev_open, .release = blkdev_close, @@ -2131,6 +2151,7 @@ const struct file_operations def_blk_fops = { .splice_read = generic_file_splice_read, .splice_write = iter_file_splice_write, .fallocate = blkdev_fallocate, + .ioinfo = blkdev_ioinfo, }; int ioctl_by_bdev(struct block_device *bdev, unsigned cmd, unsigned long arg) -- 2.11.0
next prev parent reply other threads:[~2017-02-28 14:57 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-02-28 14:57 [RFC] failure atomic writes for file systems and block devices Christoph Hellwig 2017-02-28 14:57 ` [PATCH 01/12] uapi/fs: add O_ATOMIC to the open flags Christoph Hellwig 2017-02-28 14:57 ` [PATCH 02/12] iomap: pass IOMAP_* flags to actors Christoph Hellwig 2017-02-28 14:57 ` [PATCH 03/12] iomap: add a IOMAP_ATOMIC flag Christoph Hellwig 2017-02-28 14:57 ` [PATCH 04/12] fs: add a BH_Atomic flag Christoph Hellwig 2017-02-28 14:57 ` [PATCH 05/12] fs: add a F_IOINFO fcntl Christoph Hellwig 2017-02-28 16:51 ` Darrick J. Wong 2017-03-01 15:11 ` Christoph Hellwig 2017-02-28 14:57 ` [PATCH 06/12] xfs: cleanup is_reflink checks Christoph Hellwig 2017-02-28 14:57 ` [PATCH 07/12] xfs: implement failure-atomic writes Christoph Hellwig 2017-02-28 23:09 ` Darrick J. Wong 2017-03-01 15:17 ` Christoph Hellwig 2017-02-28 14:57 ` [PATCH 08/12] xfs: implement the F_IOINFO fcntl Christoph Hellwig 2017-02-28 14:57 ` [PATCH 09/12] block: advertize max atomic write limit Christoph Hellwig 2017-02-28 14:57 ` [PATCH 10/12] block_dev: set REQ_NOMERGE for O_ATOMIC writes Christoph Hellwig 2017-02-28 14:57 ` Christoph Hellwig [this message] 2017-02-28 14:57 ` [PATCH 12/12] nvme: export the atomic write limit Christoph Hellwig 2017-02-28 20:48 ` [RFC] failure atomic writes for file systems and block devices Chris Mason 2017-02-28 20:48 ` Chris Mason 2017-03-01 15:07 ` Christoph Hellwig 2017-02-28 23:22 ` Darrick J. Wong 2017-03-01 15:09 ` Christoph Hellwig 2017-03-01 11:21 ` Amir Goldstein 2017-03-01 15:07 ` Christoph Hellwig 2017-03-01 15:07 ` Christoph Hellwig
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=20170228145737.19016-12-hch@lst.de \ --to=hch@lst.de \ --cc=linux-block@vger.kernel.org \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-xfs@vger.kernel.org \ --subject='Re: [PATCH 11/12] block_dev: implement the F_IOINFO fcntl' \ /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
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.