From: Brad Campbell <lists2009@fnarfbargle.com>
To: Roberto Spadim <roberto@spadim.com.br>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: RFC swap over raid1
Date: Fri, 02 Aug 2013 10:18:10 +0800 [thread overview]
Message-ID: <51FB16E2.8070700@fnarfbargle.com> (raw)
In-Reply-To: <CAH3kUhFvybUQ+qptd4YJj8USwOtY+HMoanTqhsE3MLtzGKFskQ@mail.gmail.com>
On 02/08/13 10:02, Roberto Spadim wrote:
> hi brad, what kernel version you was using? anyone know if the new 3.9
> and 3.10 have a badblock feature at swap?
> anyone know who control the swap? or what source files should i look
> to understand swap better?
Back then it would have been 2.2 or possibly early 2.4.
Can't really help with the other questions. I still have large amounts
of swap on all my machines for historical reasons, however it rarely
gets touched and certainly not intentionally.
I find it much nicer to be able to deal with performance issues caused
by a runaway processes forcing stuff into swap than it is to deal with
"random" processes being shot by the OOM killer.
next prev parent reply other threads:[~2013-08-02 2:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 22:11 RFC swap over raid1 Roberto Spadim
2013-08-01 23:04 ` Doug Ledford
2013-08-02 2:01 ` Roberto Spadim
2013-08-02 7:46 ` Stan Hoeppner
2013-08-02 14:21 ` Roberto Spadim
2013-08-02 15:40 ` Doug Ledford
2013-08-02 15:59 ` Roberto Spadim
2013-08-02 16:35 ` Doug Ledford
2013-08-02 16:40 ` Roberto Spadim
2013-08-02 16:50 ` Doug Ledford
2013-08-02 17:29 ` Roberto Spadim
2013-08-02 17:35 ` Doug Ledford
2013-08-02 17:38 ` Roberto Spadim
2013-08-02 18:26 ` keld
2013-08-02 18:39 ` Roberto Spadim
2013-08-02 21:31 ` Keld Jørn Simonsen
2013-08-02 15:21 ` Doug Ledford
2013-08-02 1:59 ` Brad Campbell
2013-08-02 2:02 ` Roberto Spadim
2013-08-02 2:18 ` Brad Campbell [this message]
2013-08-02 2:21 ` Roberto Spadim
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=51FB16E2.8070700@fnarfbargle.com \
--to=lists2009@fnarfbargle.com \
--cc=linux-raid@vger.kernel.org \
--cc=roberto@spadim.com.br \
/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.