[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.1.10.0805072109430.3024@woody.linux-foundation.org>
Date: Wed, 7 May 2008 21:14:45 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Andrea Arcangeli <andrea@...ranet.com>
cc: Christoph Lameter <clameter@....com>,
Andrew Morton <akpm@...ux-foundation.org>, steiner@....com,
holt@....com, npiggin@...e.de, a.p.zijlstra@...llo.nl,
kvm-devel@...ts.sourceforge.net, kanojsarcar@...oo.com,
rdreier@...co.com, swise@...ngridcomputing.com,
linux-kernel@...r.kernel.org, avi@...ranet.com, linux-mm@...ck.org,
general@...ts.openfabrics.org, hugh@...itas.com,
rusty@...tcorp.com.au, aliguori@...ibm.com, chrisw@...hat.com,
marcelo@...ck.org, dada1@...mosbay.com, paulmck@...ibm.com
Subject: Re: [PATCH 08 of 11] anon-vma-rwsem
On Thu, 8 May 2008, Andrea Arcangeli wrote:
>
> But removing sort isn't worth it if it takes away ram from the VM even
> when global_mm_lock will never be called.
Andrea, you really are a piece of work. Your arguments have been bogus
crap that didn't even understand what was going on from the beginning, and
now you continue to do that.
What exactly "takes away ram" from the VM?
The notion of adding a flag to "struct anon_vma"?
The one that already has a 4 byte padding thing on x86-64 just after the
spinlock? And that on 32-bit x86 (with less than 256 CPU's) would have two
bytes of padding if we didn't just make the spinlock type unconditionally
32 bits rather than the 16 bits we actually _use_?
IOW, you didn't even look at it, did you?
But whatever. I clearly don't want a patch from you anyway, so ..
Linus
--
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