From: Sedat Dilek <sedat.dilek@gmail.com>
To: paul.szabo@sydney.edu.au, Paul Szabo <psz@maths.usyd.edu.au>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Ben Hutchings <ben@decadent.org.uk>
Subject: Re: [RFC] Reproducible OOM with just a few sleeps
Date: Tue, 15 Jan 2013 11:25:41 +0100 [thread overview]
Message-ID: <CA+icZUUkvBDGkC8x5tUoWmOe6f8sTjLPoadTFhqgUOb91SPC9w@mail.gmail.com> (raw)
Hi Paul,
I followed a bit the thread you started in [1].
As you might know i386 got eliminated in Linux-3.8.
I had several discussions with the Debian kernel-team about the iN86
(N=4..6) and PAE kernel-flavours.
On the one hand I can understand the reduction of linux-images
especially for iN86.
Even i486 is a bit unfirm as there is no much hardware around, but
Debian will keep i486 for a while (release maintenance).
Topic PAE:
Unfortunately, I had a notebook with a Intel Centrino Banias CPU (no
PAE) which should use the -486 kernel-flavour due to the Debian
kernel-team.
I played with some different kernel-setup which did not give me more
benefit (openssl benchmarks etc.)
The -686-pae kernel did run on my hardware, but as known with all the
SMP-NO-OPs.
Depending on the hardware, it really makes sense to switch to x86_64
(amd64) architecture when you have a modern computer.
Switching makes even more sense when you have more than 4GiB RAM.
IMHO using a -686-amd64 Debian kernel makes ZERO sense, real 64-Bit or die!
I switched to 64-bit... and I switched from Debian/sid to
Ubuntu/precise as well :-).
( NOTE: I am working here since April 2012 in a WUBI environment (no
native Ubuntu Linux) :-). )
And I am building my kernels by myself.
So I know very well whom to blame :-).
Some last words: I had several fruitful or fruitless discussions with
the Debian kernel-team, but I can confirm (with all my heart) this
team makes a fantastic job.
I can recommend you Ben's blog (recently I read a series about news in
the Debian/wheezy kernel) if your world is Debian or Ubuntu (Debian !=
Ubuntu).
Just my 0.02EUR (no British pound, here as well: when you are a member
of the EU chose EUR not pound!).
Regards,
- Sedat -
[1] http://marc.info/?t=135796172200001&r=1&w=2
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2013-01-15 10:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 10:25 Sedat Dilek [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-17 21:04 [RFC] Reproducible OOM with just a few sleeps paul.szabo
2013-01-17 21:55 ` Dave Hansen
2013-01-12 19:41 paul.szabo
2013-01-12 3:31 paul.szabo
2013-01-14 15:00 ` Dave Hansen
2013-01-14 20:36 ` paul.szabo
2013-01-15 0:56 ` Dave Hansen
2013-01-15 2:16 ` paul.szabo
2013-01-30 12:51 ` Pavel Machek
2013-01-30 15:32 ` Dave Hansen
2013-01-30 19:40 ` paul.szabo
2013-02-17 9:10 ` Simon Jeons
2013-02-24 22:10 ` paul.szabo
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=CA+icZUUkvBDGkC8x5tUoWmOe6f8sTjLPoadTFhqgUOb91SPC9w@mail.gmail.com \
--to=sedat.dilek@gmail.com \
--cc=ben@decadent.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paul.szabo@sydney.edu.au \
--cc=psz@maths.usyd.edu.au \
/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).