[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200130081623.GW14879@hirez.programming.kicks-ass.net>
Date: Thu, 30 Jan 2020 09:16:23 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Michael Schmitz <schmitzmic@...il.com>
Cc: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Linux/m68k <linux-m68k@...ts.linux-m68k.org>,
Linux Kernel Development <linux-kernel@...r.kernel.org>,
Will Deacon <will@...nel.org>
Subject: Re: [PATCH 0/5] Rewrite Motorola MMU page-table layout
Hi Michael,
On Thu, Jan 30, 2020 at 08:31:13PM +1300, Michael Schmitz wrote:
> Not much difference:
>
> total used free shared buffers cached
> Mem: 10712 10120 592 0 1860 2276
> -/+ buffers/cache: 5984 4728
> Swap: 2097144 1552 2095592
>
>
> vs. vanilla 5.5rc5:
> total used free shared buffers cached
> Mem: 10716 10104 612 0 1588 2544
> -/+ buffers/cache: 5972 4744
> Swap: 2097144 1296 2095848
>
> By sheer coincidence, the boot with your patch series happened to run a full
> filesystem check on the root filesystem, so I'd say it got a good workout
> re: paging and swapping (even though it's just a paltry 4 GB).
Sweet!, can I translate this into a Tested-by: from you?
> Haven't tried any VM stress testing yet (not sure what to do for that; it's
> been years since I tried that sort of stuff).
I think, this not being SMP, doing what you just did tickled just about
everything there is.
There is one more potential issue with MMU-gather / TLB invalidate on
m68k (and a whole bunch of other archs) and I have patches for that
(although I now need to redo the m68k one.
Meanwhile the build robot gifted me with a build issue, and Will had
some nitpicks, so I'll go respin and repost these patches.
Powered by blists - more mailing lists