All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>,
	richard.weinberger@gmail.com,  computersforpeace@gmail.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mkfs.ubifs: remove the check for UBIFS_MAX_LEB_SZ
Date: Tue, 18 Aug 2015 11:52:28 +0300	[thread overview]
Message-ID: <1439887948.31419.118.camel@gmail.com> (raw)
In-Reply-To: <1439873555-5352-1-git-send-email-yangds.fnst@cn.fujitsu.com>

On Tue, 2015-08-18 at 12:52 +0800, Dongsheng Yang wrote:
> There is a commit 92ed6c0 to increase UBIFS_MAX_LEB_SZ
> to 2MiB. But recently, as the leb size become larger and
> larger, 2MiB is not a suitable limit any more.
> 
> Then remove this check in mkfs.ubifs
> 
> Signed-off-by: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
> ---
> NOTE:
> 	I am not sure the reason why we have to
> limit the leb size in mkfs.ubifs. Because
> I did not find any reason for it, I send
> this patch out. It's very possible I am
> mising something.

Well, this is sanity check for the user input. If you accidentally
added few zeroes, we want to spot this and inform you, and you may
appreciate that we did not just created a bugus image for you. That's
the idea.

Another point is that UBIFS and UBI reads eraseblocks entirely into
memory from time to time, e.g., when scanning the journal (UBIFS) or
when doing wear-levelling (UBI). Too large eraseblocks will affect the
UBI/UBIFS drivers negatively - the latency may increase significantly
(thing reading eraseblock, modifying, writing it), as well as memory
consumption.

I personally like to be strict, and if I am not sure about something, I
put limits, assuming that others may later change the limits.

That said, I'd prefer to increase the limit instead of removing it
altogether. I suggest to make it reasonably large, so that it suits
your purposes.

Artem.

  reply	other threads:[~2015-08-18  8:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18  4:52 [PATCH] mkfs.ubifs: remove the check for UBIFS_MAX_LEB_SZ Dongsheng Yang
2015-08-18  8:52 ` Artem Bityutskiy [this message]
2015-08-24  1:07   ` Dongsheng Yang
2015-08-24  6:32     ` Artem Bityutskiy
2015-08-24  6:37       ` Dongsheng Yang
2015-08-24  7:05         ` Artem Bityutskiy
2015-08-24  7:04           ` Dongsheng Yang

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=1439887948.31419.118.camel@gmail.com \
    --to=dedekind1@gmail.com \
    --cc=computersforpeace@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard.weinberger@gmail.com \
    --cc=yangds.fnst@cn.fujitsu.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 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.