linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org
Cc: viro@ZenIV.linux.org.uk
Subject: [PATCHSET 0/3] io_uring improvements
Date: Fri, 15 Mar 2019 08:59:35 -0600	[thread overview]
Message-ID: <20190315145938.21516-1-axboe@kernel.dk> (raw)

This is on top of the just posted "PATCHSET v2 0/7] io_uring fixes"
series.

This re-introduces the ability to NOT have to touch page reference
counts for our fixed buffers. Instead of assuming that's always
safe to do with a BVEC iter, we add an explicit flag for that. This
shifts the iter types a bit, but otherwise shouldn't cause any
changes.

The final patch re-adds the "we hit cache" flag. I left this out of
the initial series due to concerns over informing userspace about
this, with all the mincore etc discussions.

 block/bio.c                   | 43 +++++++++++++++++++----------------
 fs/block_dev.c                | 12 ++++++----
 fs/io_uring.c                 |  9 +++++++-
 fs/iomap.c                    | 12 ++++++----
 include/linux/blk_types.h     |  1 +
 include/linux/uio.h           | 24 +++++++++++++++----
 include/uapi/linux/io_uring.h |  5 ++++
 7 files changed, 71 insertions(+), 35 deletions(-)

-- 
Jens Axboe



             reply	other threads:[~2019-03-15 14:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15 14:59 Jens Axboe [this message]
2019-03-15 14:59 ` [PATCH 1/3] iov_iter: add ITER_BVEC_FLAG_NO_REF flag Jens Axboe
2019-03-15 14:59 ` [PATCH 2/3] block: add BIO_NO_PAGE_REF flag Jens Axboe
2019-03-15 14:59 ` [PATCH 3/3] io_uring: add io_uring_event cache hit information Jens Axboe
2019-03-15 16:27   ` Jens Axboe
2019-03-16  1:34     ` Linus Torvalds
2019-03-16 16:27       ` 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=20190315145938.21516-1-axboe@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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).