All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: 辉少 <wang502742203@qq.com>, linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: 回复：ubifs:questions about this filesystem
Date: Wed, 22 Jun 2016 21:56:39 +0200	[thread overview]
Message-ID: <576AED77.2070803@nod.at> (raw)
In-Reply-To: <tencent_47C8194435DAF0EA2221DA1E@qq.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 688 bytes --]

Hi!

Am 22.06.2016 um 17:26 schrieb »ÔÉÙ:
> Thank you for kind reply.
> 
> 1. As you said just now"there is only a background thread to do many things",  dose "many things" include both GC and synchronizing data?

I said GC can happen in many contexts. Also in the calling one.
To figure what the background thread exactly does see function ubifs_bg_thread().

> 2. If I write a file(1 KB) to ubifs mounted in 34MiB mtd, can i write 34,000 times or 34000/4 times(the real disk usage of a 1KB file is 4KB)£¿

The minimal file size on UBIFS is 4KiB. You can also not use all 34MiB, since UBIFS needs some LEBs for the journal, free space accounting,
master nodes, etc...

Thanks,
//richard

  reply	other threads:[~2016-06-22 19:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22 15:26 =?gb18030?B?u9i4tKO6dWJpZnM6cXVlc3Rpb25zIGFib3V0IHRoaXMgZmlsZXN5c3RlbQ==?= =?gb18030?B?u9TJ2Q==?=
2016-06-22 19:56 ` Richard Weinberger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-06-22 14:13 ubifs:questions about this filesystem =?gb18030?B?u9TJ2Q==?=
2016-06-22 14:26 ` Richard Weinberger
     [not found]   ` <tencent_1F5A13F32BF5625D7149E156@qq.com>
2016-06-22 14:45     ` 回复：ubifs:questions " Richard Weinberger

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=576AED77.2070803@nod.at \
    --to=richard@nod.at \
    --cc=linux-mtd@lists.infradead.org \
    --cc=wang502742203@qq.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.