From: Tony Lindgren <tony@atomide.com>
To: Paul Mundt <lethal@linux-sh.org>, Greg KH <greg@kroah.com>,
Trilok Soni <soni.trilok@gmail.com>,
Arve Hj?nnev?g <arve@android.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Pavel
Subject: Re: lowmemory android driver not needed?
Date: Tue, 3 Feb 2009 12:55:21 -0800 [thread overview]
Message-ID: <20090203205518.GI7215@atomide.com> (raw)
In-Reply-To: <20090116090210.GB7039@linux-sh.org>
* Paul Mundt <lethal@linux-sh.org> [090116 01:05]:
> On Thu, Jan 15, 2009 at 03:44:04PM -0800, Greg KH wrote:
> > On Thu, Jan 15, 2009 at 07:02:48PM +0530, Trilok Soni wrote:
> > > And there is one more lowmem driver developed by Nokia for Nokia 8xx
> > > tablets it seems. CCed Tony Lindgren, Juha and Viktor.
> > >
> > > http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=blob;f=security/lowmem.c;h=ae78a530af39703e335ad769f1e6f097f63ec6dd;hb=HEAD
> >
> > As we can't stack LSMs, using the lsm interface for a simple memory
> > driver seems pretty wasteful :)
> >
> The heuristics and tunables are more what ended up being useful with this
> module, which could trivially be abstracted out. The focus of the lowmem
> module was mostly giving userspace an opportunity to change its behaviour,
> and to try to save critical state. I don't know how well this would map
> to the Android use cases, though.
FYI, I've dropped the lowmem.c module from the linux-omap tree
considering the rest of this thread. The commit is
c00b5565aaaefadfe68d7c32d05617c81bb9edff for reference.
Regards,
Tony
next prev parent reply other threads:[~2009-02-03 20:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090114010223.GA21380@kroah.com>
[not found] ` <20090114021801.GA14759@bulgaria.corp.google.com>
[not found] ` <d6200be20901131830r7103ff8eoe0314f9faf89d89b@mail.gmail.com>
[not found] ` <20090114035237.GB16442@kroah.com>
[not found] ` <20090114104307.GA20451@elf.ucw.cz>
[not found] ` <20090114104834.18387fca@lxorguk.ukuu.org.uk>
[not found] ` <d6200be20901141426r1d48ea33gc9a380451e4aaf93@mail.gmail.com>
[not found] ` <20090114231739.GB24111@kroah.com>
[not found] ` <d6200be20901141532y6f236104kd521041d640c152e@mail.gmail.com>
[not found] ` <20090115001224.GC11328@kroah.com>
2009-01-15 13:32 ` lowmemory android driver not needed? Trilok Soni
2009-01-15 23:44 ` Greg KH
2009-01-16 9:02 ` Paul Mundt
2009-01-16 11:16 ` KOSAKI Motohiro
2009-01-16 15:23 ` Greg KH
2009-01-21 2:50 ` KOSAKI Motohiro
2009-01-21 3:05 ` Paul Mundt
2009-01-21 3:29 ` KAMEZAWA Hiroyuki
2009-04-01 18:38 ` Trilok Soni
2009-04-01 19:33 ` David Rientjes
2009-02-03 20:55 ` Tony Lindgren [this message]
2009-01-16 11:42 ` KOSAKI Motohiro
2009-01-16 13:18 ` KOSAKI Motohiro
2009-01-22 6:13 ` Arve Hjønnevåg
2009-01-29 1:48 ` KOSAKI Motohiro
2009-01-29 2:51 ` Arve Hjønnevåg
2009-01-29 3:45 ` KAMEZAWA Hiroyuki
2009-01-29 4:27 ` Greg KH
2009-01-29 4:43 ` KOSAKI Motohiro
2009-01-29 4:59 ` Greg KH
2009-01-29 5:29 ` KOSAKI Motohiro
2009-01-30 6:20 ` Greg KH
2009-01-30 6:41 ` Brian Swetland
2009-02-03 13:40 ` KOSAKI Motohiro
2009-01-29 22:06 ` Pavel Machek
2009-02-03 14:08 ` KOSAKI Motohiro
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=20090203205518.GI7215@atomide.com \
--to=tony@atomide.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arve@android.com \
--cc=greg@kroah.com \
--cc=lethal@linux-sh.org \
--cc=soni.trilok@gmail.com \
/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