From: Pavel Machek <pavel@ucw.cz>
To: Vyacheslav Dubeyko <slava@dubeyko.com>
Cc: Sooman Jeong <77smart@hanyang.ac.kr>, linux-kernel@vger.kernel.org
Subject: Re: Initial report on F2FS filesystem performance
Date: Sun, 21 Oct 2012 12:26:38 +0200 [thread overview]
Message-ID: <20121021102638.GA14031@elf.ucw.cz> (raw)
In-Reply-To: <E0328919-ACAA-4052-B922-952AFA375FD8@dubeyko.com>
Hi!
> >> This is a brief summary of our initial filesystem performance study of f2fs against existing two filesystems in linux: EXT4, NILFS2, and f2fs.
> >>
> >
> > Hmm, flashes are actually optimized for VFAT, right? Can you compare
> > against that?
> >
>
> Do you mean SD-cards? Because, as I can understand, "raw" flash (I mean NAND chip) hasn't any special filesystem-related optimization. Moreover, as I know, this optimization takes place in the begin of device (because FAT metadata is placed in the volume's begin). But if you have several partition on a device then you haven't any optimizations for second and next FAT partitions. So, in-place modified metadata of f2fs is placed in the begin of the volume also.
>
> Or, maybe, do you mean some another special optimization for VFAT?
>
I meant SD-card, sorry. Compare factory-formatted VFAT on SD card with
f2fs running on the same partition.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2012-10-21 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 4:07 Initial report on F2FS filesystem performance Sooman Jeong
2012-10-16 6:58 ` Namjae Jeon
2012-10-17 4:44 ` Sooman Jeong
2012-10-20 19:22 ` Pavel Machek
2012-10-21 9:09 ` Vyacheslav Dubeyko
2012-10-21 10:26 ` Pavel Machek [this message]
2012-10-22 11:36 ` Sooman Jeong
2012-10-23 0:07 ` Pavel Machek
2012-10-23 17:10 ` Vyacheslav Dubeyko
2012-10-30 15:36 ` Pavel Machek
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=20121021102638.GA14031@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=77smart@hanyang.ac.kr \
--cc=linux-kernel@vger.kernel.org \
--cc=slava@dubeyko.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.