[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140430141552.GA18539@redhat.com>
Date: Wed, 30 Apr 2014 16:15:52 +0200
From: Oleg Nesterov <oleg@...hat.com>
To: Benjamin LaHaise <bcrl@...ck.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Kent Overstreet <kmo@...erainc.com>,
Al Viro <viro@...iv.linux.org.uk>, linux-aio@...ck.org,
linux-kernel@...r.kernel.org
Subject: [PATCH v2 0/2] aio: ioctx_table/rcu_read_lock cleanups
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists