From: Benjamin LaHaise <bcrl@kvack.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-aio@kvack.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/7] aio: changes for 3.17
Date: Fri, 15 Aug 2014 13:23:54 -0400 [thread overview]
Message-ID: <cover.1408122224.git.bcrl@kvack.org> (raw)
Hello Linus,
Please pull the following changes from the aio-next git tree at
git://git.kvack.org/~bcrl/aio-next.git . Most of the changes this time
around are code cleanups.
-ben
Benjamin LaHaise (1):
aio: remove no longer needed preempt_disable()
Gu Zheng (4):
aio: remove the needless registration of ring file's private_data
aio: use the macro rather than the inline magic number
aio: fix some comments
aio: use iovec array rather than the single one
Oleg Nesterov (2):
aio: change exit_aio() to load mm->ioctx_table once and avoid
rcu_read_lock()
aio: kill the misleading rcu read locks in ioctx_add_table() and
kill_ioctx()
--
"Thought is the essence of where you are now."
next reply other threads:[~2014-08-15 17:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 17:23 Benjamin LaHaise [this message]
2014-08-15 17:24 ` [PATCH 1/7] aio: change exit_aio() to load mm->ioctx_table once and avoid rcu_read_lock() Oleg Nesterov
2014-08-15 17:24 ` [PATCH 2/7] aio: kill the misleading rcu read locks in ioctx_add_table() and kill_ioctx() Oleg Nesterov
2014-08-15 17:24 ` [PATCH 3/7] aio: remove no longer needed preempt_disable() Benjamin LaHaise
2014-08-15 17:24 ` [PATCH 4/7] aio: remove the needless registration of ring file's private_data Gu Zheng
2014-08-15 17:25 ` [PATCH 5/7] aio: use the macro rather than the inline magic number Gu Zheng
2014-08-15 17:25 ` [PATCH 6/7] aio: fix some comments Gu Zheng
2014-08-15 17:25 ` [PATCH 7/7] aio: use iovec array rather than the single one Gu Zheng
2014-08-16 0:35 ` Linus Torvalds
2014-08-16 1:46 ` Benjamin LaHaise
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=cover.1408122224.git.bcrl@kvack.org \
--to=bcrl@kvack.org \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@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 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.