[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181113192031.7fq5gkal62ygu6tr@soleen.tm1wkky2jk1uhgkn0ivaxijq1c.bx.internal.cloudapp.net>
Date: Tue, 13 Nov 2018 19:20:31 +0000
From: Pavel Tatashin <pasha.tatashin@...een.com>
To: Michal Hocko <mhocko@...nel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Jiri Kosina <jkosina@...e.cz>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Dave Hansen <dave.hansen@...el.com>,
Andi Kleen <ak@...ux.intel.com>, Borislav Petkov <bp@...e.de>,
LKML <linux-kernel@...r.kernel.org>, linux-mm@...ck.org,
Michal Hocko <mhocko@...e.com>
Subject: Re: [PATCH] l1tf: drop the swap storage limit restriction when
l1tf=off
On 18-11-13 19:49:10, Michal Hocko wrote:
> From: Michal Hocko <mhocko@...e.com>
>
> Swap storage is restricted to max_swapfile_size (~16TB on x86_64)
> whenever the system is deemed affected by L1TF vulnerability. Even
> though the limit is quite high for most deployments it seems to be
> too restrictive for deployments which are willing to live with the
> mitigation disabled.
>
> We have a customer to deploy 8x 6,4TB PCIe/NVMe SSD swap devices
> which is clearly out of the limit.
>
> Drop the swap restriction when l1tf=off is specified. It also doesn't
> make much sense to warn about too much memory for the l1tf mitigation
> when it is forcefully disabled by the administrator.
>
> Signed-off-by: Michal Hocko <mhocko@...e.com>
Reviewed-by: Pavel Tatashin <pasha.tatashin@...een.com>
Powered by blists - more mailing lists