[PATCH v2 0/2] aio: ioctx_table/rcu_read_lock cleanups

From: Oleg Nesterov
Date: Wed Apr 30 2014 - 10:16:14 EST

Next message: Oleg Nesterov: "[PATCH v2 1/2] aio: change exit_aio() to load mm->ioctx_table once and avoid rcu_read_lock()"
Previous message: Pawel Moll: "Re: [PATCH 02/10] mfd: vexpress: Convert custom func API to regmap"
In reply to: Oleg Nesterov: "Re: [PATCH 1/1] aio: change exit_aio() to load mm->ioctx_table once and avoid rcu_read_lock()"
Next in thread: Oleg Nesterov: "[PATCH v2 1/2] aio: change exit_aio() to load mm->ioctx_table once and avoid rcu_read_lock()"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On 04/29, Benjamin LaHaise wrote:
>
> Whoops, it's not whitespace damange, but rather that it doesn't apply with
> the other changes that are queued up in the aio-next tree. You can find a
> copy of that tree at git://git.kvack.org/~bcrl/aio-next.git . The change
> that conflicts is an additional parameter to kill_ioctx().

Please see v2. Rebased, added another untested cleanup.

Kent, it seems that you agree at least with 1/2, I'll appreciate your ack ;)

And it seems that we can kill mm->ioctx_lock, with the minimal complications
we can move it into kioctx_table, but this is minor.

Oleg.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Oleg Nesterov: "[PATCH v2 1/2] aio: change exit_aio() to load mm->ioctx_table once and avoid rcu_read_lock()"
Previous message: Pawel Moll: "Re: [PATCH 02/10] mfd: vexpress: Convert custom func API to regmap"
In reply to: Oleg Nesterov: "Re: [PATCH 1/1] aio: change exit_aio() to load mm->ioctx_table once and avoid rcu_read_lock()"
Next in thread: Oleg Nesterov: "[PATCH v2 1/2] aio: change exit_aio() to load mm->ioctx_table once and avoid rcu_read_lock()"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]