From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Dahlhoff Achim (CM-AI/PJ-CF32)" <Achim.Dahlhoff@de.bosch.com>
Cc: "Behme Dirk \(CM-AI/PJ-CF32\)" <Dirk.Behme@de.bosch.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Dirk Behme <dirk.behme@gmail.com>
Subject: Re: [PATCH] UBIFS: add tolerance to use variable writesize
Date: Mon, 01 Jul 2013 12:33:18 +0300 [thread overview]
Message-ID: <1372671198.22014.58.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <F460390DA2C115469AFACD3583F41985032D2702E7@SI-MBX07.de.bosch.com>
On Mon, 2013-07-01 at 10:32 +0200, Dahlhoff Achim (CM-AI/PJ-CF32) wrote:
> Hello.
>
> No, I do not want to touch the max_write_size or writebufsize. The
> max_write_size is the size which can be transferred in one piece to
> the chip and does not modify the UBIfs data structures.
Not sure I understand what you mean. Max_write_size, which is the same
as writebufsize, despite the name, is the _optimal_ I/O size. Sometimes
UBI/UBIFS _will_ write in smaller chunks. But it will try to write in
'max_write_size'.
Sounds like what you need - you flash does allow 1-byte writes, but will
be more efficient when writes are 32-bytes instead.
> The min size is relevant and can cause images to become incompatible
> with a specific NOR chip. If the NOR driver should accidentally choose
> a writesize which is too small, this will not cause any compatibility
> issues or data loss. It will only reduce write performance.
Right, increasing min_io_size breaks compatibility. Although I believe
this is fixable, and I already suggested people to fix this several
times in the past.
But increasing max_write_size should not lead to incompatibilites.
>
> Without the tolerance patch, you cannot mount one UBSfs image on
> different NOR devices with different writesize values of 1 or 32.
I still think that you should just change writebufsize in your driver.
May be you could find some other view-angle to show my why you think I
am wrong?
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2013-07-01 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 16:21 [PATCH] UBIFS: add tolerance to use variable writesize Dirk Behme
2013-07-01 7:55 ` Artem Bityutskiy
2013-07-01 8:32 ` Dahlhoff Achim (CM-AI/PJ-CF32)
2013-07-01 9:33 ` Artem Bityutskiy [this message]
2013-07-04 11:50 ` Dirk Behme
[not found] <1369237284-3559-1-git-send-email-dirk.behme@gmail.com>
2013-05-22 15:43 ` Dirk Behme
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=1372671198.22014.58.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=Achim.Dahlhoff@de.bosch.com \
--cc=Dirk.Behme@de.bosch.com \
--cc=dirk.behme@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.