From: Andi Kleen <ak@linux.intel.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Jiri Kosina <jkosina@suse.cz>,
Linus Torvalds <torvalds@linux-foundation.org>,
Dave Hansen <dave.hansen@intel.com>, Borislav Petkov <bp@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH] l1tf: drop the swap storage limit restriction when l1tf=off
Date: Wed, 14 Nov 2018 16:27:44 -0800 [thread overview]
Message-ID: <20181115002744.GM6218@tassilo.jf.intel.com> (raw)
In-Reply-To: <20181113184910.26697-1-mhocko@kernel.org>
On Tue, Nov 13, 2018 at 07:49:10PM +0100, Michal Hocko wrote:
> From: Michal Hocko <mhocko@suse.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.
Reviewed-by: Andi Kleen <ak@linux.intel.com>
-Andi
next prev parent reply other threads:[~2018-11-15 0:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 18:49 [PATCH] l1tf: drop the swap storage limit restriction when l1tf=off Michal Hocko
2018-11-13 19:20 ` Pavel Tatashin
2018-11-13 19:56 ` Jiri Kosina
2018-11-14 7:32 ` Michal Hocko
2018-11-19 13:36 ` Jiri Kosina
2018-11-19 13:51 ` Michal Hocko
2018-12-09 20:46 ` Jiri Kosina
2018-12-10 20:03 ` Michal Hocko
2018-11-15 0:27 ` Andi Kleen [this message]
2018-12-10 21:09 ` [tip:x86/pti] x86/speculation/l1tf: Drop " tip-bot for Michal Hocko
2018-12-11 9:00 ` Ingo Molnar
2018-12-11 10:47 ` Thomas Gleixner
2018-12-11 11:13 ` Michal Hocko
2018-12-11 10:36 ` tip-bot for Michal Hocko
2018-12-11 10:51 ` tip-bot for Michal Hocko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181115002744.GM6218@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=bp@suse.de \
--cc=dave.hansen@intel.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).