[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1383362336.2444.8.camel@buesod1.americas.hpqcorp.net>
Date: Fri, 01 Nov 2013 20:18:56 -0700
From: Davidlohr Bueso <davidlohr@...com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Michel Lespinasse <walken@...gle.com>,
Andrea Arcangeli <aarcange@...hat.com>,
Ingo Molnar <mingo@...nel.org>,
Yuanhan Liu <yuanhan.liu@...ux.intel.com>,
Tim Chen <tim.c.chen@...ux.intel.com>,
Davidlohr Bueso <davidlohr.bueso@...com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Rik van Riel <riel@...hat.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCH 0/4] per anon_vma lock and turn anon_vma rwsem lock to
rwlock_t
On Fri, 2013-11-01 at 11:55 -0700, Linus Torvalds wrote:
> On Fri, Nov 1, 2013 at 11:47 AM, Michel Lespinasse <walken@...gle.com> wrote:
> >
> > Should copy Andrea on this. I talked with him during KS, and there are
> > no current in-tree users who are doing such sleeping; however there
> > are prospective users for networking (RDMA) or GPU stuff who want to
> > use this to let hardware directly copy data into user mappings.
>
> Tough.
>
> I spoke up the first time this came up and I'll say the same thing
> again: we're not screwing over the VM subsystem because some crazy
> user might want to do crazy and stupid things that nobody sane cares
> about.
>
> The whole "somebody might want to .." argument is just irrelevant.
Ok, I was under the impression that this was something already in the
kernel and hence "too late to go back". Based on the results I'm
definitely in favor of the whole rwlock conversion.
Thanks,
Davidlohr
--
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