From: Alexander Belyakov <alexander.belyakov@intel.com>
To: Nicolas Pitre <nico@cam.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] MTD: mtdconcat NAND/Sibley support
Date: Thu, 27 Apr 2006 12:32:52 +0400 [thread overview]
Message-ID: <445081B4.8070801@intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0604261157030.18520@localhost.localdomain>
Nicolas Pitre wrote:
>
> That won't work with Sibley.
>
It does work for Sibley. I've checked it for both NAND and Sibley before
posting.
> Sibley flash must write everything all at once with
> a single writev call.
>
Not sure what did you mean by that. But I should say that
concat_writev() function does writes by page-sized chunks even if one
vector entry has size less than one page. Function just "glues" it with
the next vector entry (or its part) if any. So there are no writes with
size less than pagesize, except first and last pages if we have
unaligned data in downcoming vector.
As for too "complex" patch implementation. I'll take a look what can be
done with usage of writev() and writev_ecc() of underlying devices.
Thank you for advice. But as I said this change is just design matter
and will not benefit much, because underlying device writev() function
have to do the pagesize chunks splitting anyway.
Alexander
-------
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue
next prev parent reply other threads:[~2006-04-27 8:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 11:36 [PATCH] MTD: mtdconcat NAND/Sibley support Belyakov, Alexander
2006-04-26 14:16 ` Jörn Engel
2006-04-26 15:21 ` Alexander Belyakov
2006-04-26 15:57 ` Jörn Engel
2006-04-26 15:51 ` Jörn Engel
2006-04-27 8:46 ` Alexander Belyakov
2006-05-03 16:22 ` Thomas Gleixner
2006-04-26 16:04 ` Nicolas Pitre
2006-04-26 16:08 ` Jörn Engel
2006-04-26 16:26 ` Nicolas Pitre
2006-04-27 8:32 ` Alexander Belyakov [this message]
2006-04-27 13:02 ` Nicolas Pitre
2006-04-27 13:46 ` Alexander Belyakov
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=445081B4.8070801@intel.com \
--to=alexander.belyakov@intel.com \
--cc=linux-mtd@lists.infradead.org \
--cc=nico@cam.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