mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: cgxu519 <cgxu519@gmx.com>
To: Gao Xiang <gaoxiang25@huawei.com>
Cc: Gao Xiang <hsiangkao@aol.com>,
	linux-erofs@lists.ozlabs.org, devel@driverdev.osuosl.org,
	LKML <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"liguifu (C)" <bluce.liguifu@huawei.com>,
	"fangwei (I)" <fangwei1@huawei.com>, Chao Yu <yuchao0@huawei.com>,
	Miao Xie <miaoxie@huawei.com>
Subject: Re: How can I get user space tools of erofs?
Date: Mon, 12 Nov 2018 09:51:36 +0800	[thread overview]
Message-ID: <24438b2f-1676-3718-18cc-7c99aa2a7741@gmx.com> (raw)
In-Reply-To: <923d8f98-bd0c-47e1-63a5-512547d6a77d@huawei.com>


> Hi Chengguang,
>
> Good question! It's in the final stage of preparation to open source erofs-mkfs (actually they are now struggle at how to properly spilt
> into reasonable patches this week), hopefully the implementation could be released at the next week. (sorry I didn't mean to delay,
> I have to put it in the first place --- successfully launch our linux-erofs products to the market)
>
> @Guifu Li <bluce.liguifu@huawei.com> is the original author of erofs-mkfs, he will post the original mkfs source code to linux-erofs mailing list
> and he will maintain erofs-mkfs together with @Wei Fang <fangwei1@huawei.com> later. You can contact them for further informations.
> ---  these piece of code is actually not clean enough (a lot hacked/dirty code compared to the kernel code) so a lot of cleanup will be done then.
>
> currently, you can get erofs-mkfs binary from (still sorry to say that...):
> https://github.com/hsiangkao/erofs_mkfs_binary
>
> erofs is now in productization for these months, if all things go well, you'll see that HUAWEI mobile phones on the market run in erofs in few months. :)
>
> These months I'm busy in solving bugs found by internal beta users and tuning memory policy in heavy memory workload for the best performance compared to ext4
> (we have native in-place decompression compared with squashfs/btrfs, thus less extra memory allocation results in lower memory memory reclaim / page-writeback
> for devices with limited memory, see: https://lists.ozlabs.org/pipermail/linux-erofs/2018-August/000494.html) in order to gain the competitive user experience
> comparing to uncompressed filesystem solutions. I will update a document to describe our core design and linux-erofs future roadmap in this linux-4.21 round.

Hi Xiang,

Thanks for your detail explanations!

Chengguang




      reply	other threads:[~2018-11-12  1:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cce741a4-8e15-a48c-070e-d16d71b864c3@gmx.com>
2018-11-09 11:38 ` Gao Xiang
2018-11-12  1:51   ` cgxu519 [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=24438b2f-1676-3718-18cc-7c99aa2a7741@gmx.com \
    --to=cgxu519@gmx.com \
    --cc=bluce.liguifu@huawei.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=fangwei1@huawei.com \
    --cc=gaoxiang25@huawei.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hsiangkao@aol.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miaoxie@huawei.com \
    --cc=yuchao0@huawei.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

all inboxes | Powered by JetHome®