From: Artem Bityutskiy <dedekind@infradead.org>
To: Alexey Korolev <akorolev@infradead.org>
Cc: linux-mtd@lists.infradead.org, dwmw2@infradead.org
Subject: Re: [PATCH][nandsim] FIX RAM wasting via kmalloc
Date: Mon, 27 Oct 2008 09:18:46 +0200 [thread overview]
Message-ID: <1225091926.3833.2.camel@sauron> (raw)
In-Reply-To: <alpine.LFD.1.10.0810221611550.30499@casper.infradead.org>
Alexey,
On Wed, 2008-10-22 at 16:33 +0100, Alexey Korolev wrote:
> Nandsim consumes ~2x more RAM than the density of simulated device.
> It becomes critical if we need to simulate 256MB NAND and run stress tests
> on it.
I'm applying your patch to our local tree, just to test it. But there
is a trailing white-space.
[dedekind@gollum ubifs-2.6]$ git-am nandsim
Applying FIX RAM wasting via kmalloc
.dotest/patch:64: trailing whitespace.
* then kernel memory alloc runs writeback which goes to
the FS
warning: 1 line adds whitespace errors.
:-)
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-10-27 7:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 15:33 [PATCH][nandsim] FIX RAM wasting via kmalloc Alexey Korolev
2008-10-22 15:49 ` Artem Bityutskiy
2008-10-27 7:18 ` Artem Bityutskiy [this message]
2008-10-27 12:59 ` Alexey Korolev
2008-10-29 9:27 ` Artem Bityutskiy
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=1225091926.3833.2.camel@sauron \
--to=dedekind@infradead.org \
--cc=akorolev@infradead.org \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.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