[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190312172157.GC32504@tower.DHCP.thefacebook.com>
Date: Tue, 12 Mar 2019 17:22:02 +0000
From: Roman Gushchin <guro@...com>
To: Matthew Wilcox <willy@...radead.org>
CC: "Tobin C. Harding" <me@...in.cc>,
"Tobin C. Harding" <tobin@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Christoph Lameter <cl@...ux.com>,
Pekka Enberg <penberg@...nel.org>,
David Rientjes <rientjes@...gle.com>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/4] mm: Use slab_list list_head instead of lru
On Mon, Mar 11, 2019 at 07:38:28PM -0700, Matthew Wilcox wrote:
> On Tue, Mar 12, 2019 at 12:05:54PM +1100, Tobin C. Harding wrote:
> > > slab_list and lru are in the same bits. Once this patch set is in,
> > > we can remove the enigmatic 'uses lru' comment that I added.
> >
> > Funny you should say this, I came to me today while daydreaming that I
> > should have removed that comment :)
> >
> > I'll remove it in v2.
>
> That's great. BTW, something else you could do to verify this patch
> set is check that the object file is unchanged before/after the patch.
> I tend to use 'objdump -dr' to before.s and after.s and use 'diff'
> to compare the two.
Btw, is it guaranteed that the object file will not change?
I was about to recommend the same, but was not sure, if such change
can cause gcc to generate a *slightly* different obj code.
Thanks!
Powered by blists - more mailing lists