public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: "余华兵(平台一部 福州)" <yhb@ruijie.com.cn>,
	"'Richard Weinberger'" <richard@nod.at>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Cc: "俞寿华(平台一部 福州)" <yushouhua@ruijie.com.cn>,
	"邓文杰(平台一部 福州)" <dengwenjie@ruijie.com.cn>,
	"黄崇滨(平台一部 福州)" <huangcb@ruijie.com.cn>,
	"江信辉(平台一部 福州)" <jiangxh@ruijie.com.cn>
Subject: Re: 答复: UBIFS: Failed to read/write file when contiguous pages are not enough
Date: Tue, 21 Mar 2017 09:30:31 +0200	[thread overview]
Message-ID: <1490081431.11326.75.camel@gmail.com> (raw)
In-Reply-To: <80B78A8B8FEE6145A87579E8435D78C307988C07@FZEX3.ruijie.com.cn>

On Tue, 2017-03-21 at 01:53 +0000, 余华兵(平台一部 福州) wrote:
> Or does this only happen when the kernel tries to produce free memory
> in the writeback path?
> //This happens when UBIFS reads or writes a file. UBIFS should avoid
> applying for continuous pages, otherwise it will fail when the
> continuous pages are not enough.

You are right that it will be better if UBIFS allocates single pages
only. But this is an improvement request. It is not a bug to do order 1
allocations, it is just an imperfection: UBIFS could work better on
system with highly fragmented memory.

Artem.

      parent reply	other threads:[~2017-03-21  7:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <80B78A8B8FEE6145A87579E8435D78C3079814E8@FZEX3.ruijie.com.cn>
2017-03-20  9:14 ` UBIFS: Failed to read/write file when contiguous pages are not enough Richard Weinberger
     [not found]   ` <80B78A8B8FEE6145A87579E8435D78C307988C07@FZEX3.ruijie.com.cn>
2017-03-21  7:30     ` 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=1490081431.11326.75.camel@gmail.com \
    --to=dedekind1@gmail.com \
    --cc=dengwenjie@ruijie.com.cn \
    --cc=huangcb@ruijie.com.cn \
    --cc=jiangxh@ruijie.com.cn \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=yhb@ruijie.com.cn \
    --cc=yushouhua@ruijie.com.cn \
    /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