public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Alexander Belyakov <alexander.belyakov@intel.com>
To: Jorn Engel <joern@wohnheim.fh-wedel.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] MTD: mtdconcat NAND/Sibley support
Date: Wed, 26 Apr 2006 19:21:38 +0400	[thread overview]
Message-ID: <444F9002.9060000@intel.com> (raw)
In-Reply-To: <20060426141609.GG29108@wohnheim.fh-wedel.de>

Jorn Engel wrote:
>
> concat_writev() is far too complicated.  I have a patch somewhere that
> adds a generic writev() function to every device.  Once that is in,
> your patch should get a respin and be much simpler.
>

Having generic writev() still requires concat_writev() to split the data 
into several parts (in general case by number of subdevices). So I do 
not see how concat_writev() could become simpler.

In my patch you split data from downcoming vector into several  _equal_  
page-sized chunks and write them by calling generic write().

In case you think about one have to create  _several_vectors_  of  
_unknown_  size and pass them to the generic writev() which in turn will 
anyway split these new vectors into equal page-sized chunks.

And I really doubt there is a way to simplify concat_block_isbad() and 
concat_block_markbad() functions from the patch.

> I didn't closely look at the rest of it but suspect similar things.
>

Why I'm not surprised here? :)

Patch have nothing complex and have completely nothing new. Just fixes 
some broken stuff.

Is it better to leave concatenation layer without any changes and only 
compatible with NOR devices, despite mtdconcat.c file comments claim 
that it does support NAND?

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

  reply	other threads:[~2006-04-26 15:22 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 [this message]
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
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=444F9002.9060000@intel.com \
    --to=alexander.belyakov@intel.com \
    --cc=joern@wohnheim.fh-wedel.de \
    --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