From: Valdis.Kletnieks@vt.edu
To: Hugh Dickins <hughd@google.com>
Cc: Shaohua Li <shli@kernel.org>,
Sasha Levin <sasha.levin@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Shaohua Li <shli@fusionio.com>, Rik van Riel <riel@redhat.com>,
Minchan Kim <minchan@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: boot warnings due to swap: make each swap partition have one address_space
Date: Tue, 29 Jan 2013 10:56:12 -0500 [thread overview]
Message-ID: <10359.1359474972@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sun, 27 Jan 2013 13:40:40 -0800." <alpine.LNX.2.00.1301271321500.16981@eggly.anvils>
[-- Attachment #1: Type: text/plain, Size: 509 bytes --]
On Sun, 27 Jan 2013 13:40:40 -0800, Hugh Dickins said:
> My reservations so far would be: how many installations actually have
> more than one swap area, so is it a good tradeoff to add more overhead
> to help those at the (slight) expense of everyone else? The increasingly
> ugly page_mapping() worries me, and the static array of swapper_spaces
> annoys me a little.
Right now, probably few. But the number may go up a lot if the whole
'zram-for-swapspace' thing catches on and/or ships in a distro...
[-- Attachment #2: Type: application/pgp-signature, Size: 865 bytes --]
next prev parent reply other threads:[~2013-01-29 15:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 3:45 Sasha Levin
2013-01-25 4:25 ` Shaohua Li
2013-01-25 23:37 ` Sasha Levin
2013-01-27 2:16 ` Hugh Dickins
2013-01-27 14:12 ` Shaohua Li
2013-01-27 21:40 ` Hugh Dickins
2013-01-29 15:56 ` Valdis.Kletnieks [this message]
2013-01-30 9:59 ` Shaohua Li
2013-02-04 5:12 ` Hugh Dickins
2013-01-27 21:47 ` [PATCH next/mmotm] swap: add per-partition lock for swapfile fix Hugh Dickins
2013-01-28 0:07 ` Shaohua Li
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=10359.1359474972@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=riel@redhat.com \
--cc=sasha.levin@oracle.com \
--cc=shli@fusionio.com \
--cc=shli@kernel.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