From: Michal Hocko <mhocko@suse.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: terminal fault
Date: Thu, 19 Apr 2018 09:41:51 +0200 [thread overview]
Message-ID: <20180419074151.GP17484@dhcp22.suse.cz> (raw)
In-Reply-To: <nycvar.YFH.7.76.1804190929390.28129@cbobk.fhfr.pm>
On Thu 19-04-18 09:33:31, speck for Jiri Kosina wrote:
> On Thu, 19 Apr 2018, speck for Michal Hocko wrote:
>
> > we might be more anal and fail to swap on such a large partitions/files
> > but I do not see much point making this more complicated than necessary.
>
> I think that issuing WARN_ON_ONCE() somewhere in swapon() in cases where
> the swap is too big so that it doesn't cover it for maximum pfn on given
> microarchitecture (&& in case we're running on affected CPU, which for
> starters will mean empty whitelist) could be reasonable.
Do we have that max pfn per uarch?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-04-19 7:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 8:35 [MODERATED] terminal fault Michal Hocko
2018-04-18 13:36 ` [MODERATED] " Jon Masters
2018-04-18 14:46 ` Konrad Rzeszutek Wilk
2018-04-19 7:28 ` Michal Hocko
2018-04-19 7:33 ` Jiri Kosina
2018-04-19 7:41 ` Michal Hocko [this message]
2018-04-19 7:52 ` Jiri Kosina
2018-04-19 17:02 ` Jon Masters
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=20180419074151.GP17484@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=speck@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.