linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: jaegeuk.kim@samsung.com, linux-f2fs-devel@lists.sourceforge.net,
	kernel list <linux-kernel@vger.kernel.org>
Subject: f2fs tests
Date: Fri, 21 Jun 2013 21:36:00 +0200	[thread overview]
Message-ID: <20130621193600.GA12712@amd.pavel.ucw.cz> (raw)

Hi!

I played a bit with f2fs...

First, I had to compile the f2fstools... Unfortunately they require
never autoconf than available on debian. I tried to hack it, but then
I decided that compiling it by hand is just simpler.

gcc -I include/ -I . lib/*.c mkfs/*.c /usr/lib/libuuid.so

does the trick.

I was quite surprised there's no fsck in the repository... Do you have
fsck somewhere?

I tested with copy of kernel and 4GB stick (with RedHat logo, thanks
:-)... copying it from hdd took 46 minutes for VFAT and 19 minutes for
F2FS. Good.

VFAT: time find . -name "not-here" took 26 seconds.
F2F:  time find . -name "not-here" took 22-24 seconds.

Faster copy, same speed find, good. (Find is even slightly faster than
HDD, with 27-30 seconds).

But now the strange stuff: the same data takes 861MB on ext3 and 1.3GB
on f2fs. (It was even bigger than that on VFAT). I guess I should test
the patch for inlining small files into inodes?

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

             reply	other threads:[~2013-06-21 19:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-21 19:36 Pavel Machek [this message]
2013-06-25  5:13 ` f2fs tests Jaegeuk Kim

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=20130621193600.GA12712@amd.pavel.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=jaegeuk.kim@samsung.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).