public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Alexey Korolev <akorolev@infradead.org>
Cc: Hamish Moffatt <hamish@cloud.net.au>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-mtd@lists.infradead.org, dwmw2@infradead.org
Subject: Re: [RFC][patch] NAND partial page read functionality
Date: Thu, 24 Apr 2008 13:45:53 +0300	[thread overview]
Message-ID: <1209033953.11721.131.camel@sauron> (raw)
In-Reply-To: <Pine.LNX.4.64.0804241057520.6029@pentafluge.infradead.org>

Hi,

On Thu, 2008-04-24 at 11:25 +0100, Alexey Korolev wrote:
> Oh I'm glad to hear that this patch is needful. In fact I did
> not drop it. We did some more investigations about integration subpage
>  read in background. We tried to remove some drawback caused by
> invalidation of prestored page in do_read_ops function. (We have found
> that on large read requests nand subpage read causes ~10% of read performance degradation. I
> wanted to remove but changes made code ugly and saved only 5%)

Err, are you referring this chip->pagebuf cache? Have you considered
making it more complex and keep track of individual sub-pages within the
pagebuf? You say it introduces a lot of ugliness? May be you could
somehow separate this ugliness out nicely somehow?

> Also we investigated possibility to make more universal solution which includes both sub-page 
> read and partial page write. As it was discussed in December. In fact the partial page write did not
> give any benefits at all as file system operates write_size. If we reduce writesize JFFS2 will write data by 
> small chunks only and it will cause strong performance degradation. (it
> brings more cons than pros until serious hacks in JFFS2 will be
> implemented)

Well, in any case, if you have something for writes, this should be a
separate story.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2008-04-24 10:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13 18:15 [RFC][patch] NAND partial page read functionality Alexey Korolev
2007-12-15 12:13 ` Artem Bityutskiy
2007-12-17 15:46   ` Alexey Korolev
2007-12-18  8:48     ` Artem Bityutskiy
2007-12-18 11:42       ` Jörn Engel
2007-12-18 12:57         ` Artem Bityutskiy
2007-12-18 13:51           ` Jörn Engel
2008-04-24  6:34 ` Artem Bityutskiy
2008-04-24  7:11   ` Artem Bityutskiy
2008-04-24  7:45   ` Hamish Moffatt
2008-04-24  9:53     ` Artem Bityutskiy
2008-04-24 10:25     ` Alexey Korolev
2008-04-24 10:45       ` Artem Bityutskiy [this message]
2008-04-24 10:57         ` Alexey Korolev
2008-04-24 14:04       ` Hamish Moffatt
2008-04-24 14:48         ` Alexey Korolev

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=1209033953.11721.131.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=akorolev@infradead.org \
    --cc=dwmw2@infradead.org \
    --cc=hamish@cloud.net.au \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tglx@linutronix.de \
    /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