[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130615174657.GA15550@redhat.com>
Date: Sat, 15 Jun 2013 19:46:57 +0200
From: Oleg Nesterov <oleg@...hat.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Al Viro <viro@...iv.linux.org.uk>,
Andrey Vagin <avagin@...nvz.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
David Howells <dhowells@...hat.com>,
linux-kernel@...r.kernel.org, Huang Ying <ying.huang@...el.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCH 0/3] (Was: fput: task_work_add() can fail if the caller
has passed exit_task_work())
sorry, forgot to mention...
On 06/15, Oleg Nesterov wrote:
>
> > OT: I don't think that schedule_work() needs to be inside the locked
> > region. Scalability improvements beckon!
>
> Yeees, I thought about this too.
>
> Performance-wise this can't really help, this case is unlikely. But
> I think this change makes this code a bit simpler, so please see 1/3.
This is on top of
fput-task_work_add-can-fail-if-the-caller-has-passed-exit_task_work-fix.patch
it textually depends on the comment block in fput() added by that patch.
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