From: Benjamin LaHaise <bcrl@kvack.org>
To: linux-aio@kvack.org, Gu Zheng <guz.fnst@cn.fujitsu.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, linux-fsdevel@kvack.org
Subject: summary of current pending changes in aio-next.git
Date: Thu, 8 Aug 2019 12:14:57 -0400 [thread overview]
Message-ID: <20190808161457.GP28371@kvack.org> (raw)
The first 10 of Kent's AIO optimization series have been pulled into my
tree as summarised below. I had to rework some of the patches to correctly
apply after Gu Zheng's polishing of the AIO ringbuffer migration support,
so any extra eyes on those changes would be helpful. I also fixed a couple
of bugs in the table lookup patch, as well as eliminating a BUG_ON() Kent
added in order to be a bit more defensive.
These changes should show up in linux-next, so please give them a beating.
I plan to post a few more changes against this tree in the next couple of
weeks.
-ben
---
The following changes since commit 47188d39b5deeebf41f87a02af1b3935866364cf:
Merge tag 'ext4_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4 (2013-07-14 21:47:51 -0700)
are available in the git repository at:
git://git.kvack.org/~bcrl/aio-next.git master
for you to fetch changes up to 6878ea72a5d1aa6caae86449975a50b7fe9abed5:
aio: be defensive to ensure request batching is non-zero instead of BUG_ON() (2013-07-31 10:34:18 -0400)
----------------------------------------------------------------
Benjamin LaHaise (4):
aio: fix build when migration is disabled
aio: double aio_max_nr in calculations
aio: convert the ioctx list to table lookup v3
aio: be defensive to ensure request batching is non-zero instead of BUG_ON()
Gu Zheng (2):
fs/anon_inode: Introduce a new lib function anon_inode_getfile_private()
fs/aio: Add support to aio ring pages migration
Kent Overstreet (9):
aio: reqs_active -> reqs_available
aio: percpu reqs_available
aio: percpu ioctx refcount
aio: io_cancel() no longer returns the io_event
aio: Don't use ctx->tail unnecessarily
aio: Kill aio_rw_vect_retry()
aio: Kill unneeded kiocb members
aio: Kill ki_users
aio: Kill ki_dtor
drivers/staging/android/logger.c | 2 +-
drivers/usb/gadget/inode.c | 9 +-
fs/aio.c | 717 +++++++++++++++++++++++++--------------
fs/anon_inodes.c | 66 ++++
fs/block_dev.c | 2 +-
fs/nfs/direct.c | 1 -
fs/ocfs2/file.c | 6 +-
fs/read_write.c | 3 -
fs/udf/file.c | 2 +-
include/linux/aio.h | 21 +-
include/linux/anon_inodes.h | 3 +
include/linux/migrate.h | 3 +
include/linux/mm_types.h | 5 +-
kernel/fork.c | 2 +-
mm/migrate.c | 2 +-
mm/page_io.c | 1 -
net/socket.c | 15 +-
17 files changed, 549 insertions(+), 311 deletions(-)
--
"Thought is the essence of where you are now."
reply other threads:[~2019-08-08 16:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190808161457.GP28371@kvack.org \
--to=bcrl@kvack.org \
--cc=guz.fnst@cn.fujitsu.com \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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).