From: Artem Bityutskiy <dedekind1@gmail.com>
To: Murali N <nalajala.murali@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Data read/write request length in UBIFS!!!
Date: Wed, 21 Apr 2010 19:42:43 +0300 [thread overview]
Message-ID: <1271868163.11751.1398.camel@localhost.localdomain> (raw)
In-Reply-To: <r2u630851df1004210932u61ea3cf8hb3a1372512855079@mail.gmail.com>
On Wed, 2010-04-21 at 22:02 +0530, Murali N wrote:
> Hi,
> I have few basic doubt on UBIFS/UBI.
>
> At present i am seeing some 64 bytes read request coming while doing
> the "ubiattach" on one of the MTD partition.
Why is this a problem?
> What's the typical read/write length request that come's from the UBIFS?
It depends of what is being read. Sometimes these are few bytes (reading
LPT or a direntry), sometimes 1-2 pages (reading file data), sometimes
whole eraseblock (GC-ing).
> In a normal scenario read/write requests to flash would be multiple of
> flash page size? or it could be of any size?
Any size.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-04-21 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 16:32 Data read/write request length in UBIFS!!! Murali N
2010-04-21 16:42 ` Artem Bityutskiy [this message]
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=1271868163.11751.1398.camel@localhost.localdomain \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=nalajala.murali@gmail.com \
/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