[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPv3WKdYdwpi3k5eY86qibfprMFwkYOkDwHOsNydp=0sTV3mgg@mail.gmail.com>
Date: Tue, 31 May 2016 12:29:51 +0200
From: Marcin Wojtas <mw@...ihalf.com>
To: Robin Murphy <robin.murphy@....com>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Lior Amsalem <alior@...vell.com>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
Yehuda Yitschak <yehuday@...vell.com>,
Catalin Marinas <catalin.marinas@....com>,
Arnd Bergmann <arnd@...db.de>,
Grzegorz Jaszczyk <jaz@...ihalf.com>,
Will Deacon <will.deacon@....com>, nadavh@...vell.com,
Tomasz Nowicki <tn@...ihalf.com>,
Gregory Clément
<gregory.clement@...e-electrons.com>
Subject: Re: [BUG] Page allocation failures with newest kernels
Hi Robin,
>
> I remember there were some issues around 4.2 with the revision of the arm64
> atomic implementations affecting the cmpxchg_double() in SLUB, but those
> should all be fixed (and the symptoms tended to be considerably more fatal).
> A stronger candidate would be 97303480753e (which landed in 4.4), which has
> various knock-on effects on the layout of SLUB internals - does fiddling
> with L1_CACHE_SHIFT make any difference?
>
I'll check the commits, thanks. I forgot to add L1_CACHE_SHIFT was my
first suspect - I had spent a long time debugging network controller,
which stopped working because of this change - L1_CACHE_BYTES (and
hence NET_SKB_PAD) not fitting HW constraints. Anyway reverting it
didn't help at all for page alloc issue.
Best regards,
Marcin
Powered by blists - more mailing lists