From: Roland Eggner <edvx1@systemanalysen.net>
To: Dimitrios Apostolou <jimis@gmx.net>
Cc: linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
"Theodore Ts'o" <tytso@mit.edu>
Subject: Re: backing up ext4 fs, system unresponsive, thrashing like crazy even though swap is unused
Date: Mon, 3 Dec 2012 19:03:18 +0100 [thread overview]
Message-ID: <20121203180318.GA22323@mobil.systemanalysen.net> (raw)
In-Reply-To: <alpine.LFD.2.02.1212030120090.1646@soupermouf>
[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]
On 2012-12-03 Monday at 01:56 +0200 Dimitrios Apostolou wrote:
> Dear Ronald,
Excuse me, my name is Roland.
> sorry for not replying at your first message but I didn't consider changing
> kernel as a resolution to my problem.
>
> … …
> > … …
> > One advantage of Linux compared to other OS is much more support for old
> > hardware, if a _proper_ kernel version is selected. Many years ago I used
> > a notebook with 40 M total RAM, with a 2.4 kernel, Blackbox window manager and
> > Opera web browser … it worked flawlessly … just rather slowly due to swapping.
> > Your notebook has much more RAM than 40 M, thus there is surely a Linux solution
> > for you. Try a 2.6.27.62 kernel, it supports ext4 (“ext4dev”), probably it
> > supports all devices of your notebook, and with a slim window manager e.g.
> > WindowMaker or OpenBox your notebook will probably “fly”.
>
> I appreciate your advice. I remember when we were running 2.4 much less
> memory was needed, but still I consider the kernel /fairly/ lean
> considering the time passed and the bloat in userspace applications. I
> choose to run latest kernels on old hardware, hopefully this will continue
> to be the case, and if things deteriorate much then let's hope we'll have
> enough time to help and fix them! :-)
Ok, this is another story: You are not looking for a least-effort solution just
for your notebook. Instead you want to contribute to the LMKL community
solutions how to run current kernel versions under extremly tight memory
limitations like with your notebook, right? If so: This is highly appreciated,
thank you! I will interestingly read your findings :)
--
Roland
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-12-03 18:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-25 15:03 backing up ext4 fs, system unresponsive, thrashing like crazy even though swap is unused Dimitrios Apostolou
2012-12-02 12:44 ` Dimitrios Apostolou
2012-12-02 22:50 ` Roland Eggner
2012-12-02 23:56 ` Dimitrios Apostolou
2012-12-03 17:43 ` Theodore Ts'o
2012-12-03 18:47 ` Eric Paris
2012-12-03 19:35 ` Dimitrios Apostolou
2012-12-03 20:00 ` Dimitrios Apostolou
2012-12-03 18:03 ` Roland Eggner [this message]
2012-12-03 19:25 ` Dimitrios Apostolou
[not found] <1353851735.22969.18.camel@soupermouf>
2012-11-25 19:30 ` Dimitrios Apostolou
2012-11-25 22:59 ` Roland Eggner
2012-11-25 23:56 ` Alan Cox
2012-11-26 3:11 ` Roland Eggner
2012-12-06 14:20 ` Jan Kara
2012-12-06 15:15 ` Dimitrios Apostolou
2012-12-06 16:43 ` Jan Kara
2012-12-07 15:26 ` Dimitrios Apostolou
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=20121203180318.GA22323@mobil.systemanalysen.net \
--to=edvx1@systemanalysen.net \
--cc=catalin.marinas@arm.com \
--cc=jimis@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.