From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: Paul Ni <nikulinpi@gmail.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: Segment size
Date: Fri, 09 May 2014 09:11:56 +0900 [thread overview]
Message-ID: <1399594316.13268.63.camel@kjgkr> (raw)
In-Reply-To: <CAN3U_kVBpbuaOQn6Q=obm5GmfOUdCLahWp6DXvUSaYnRj=frvA@mail.gmail.com>
2014-05-08 (목), 12:43 -0700, Paul Ni:
> On 6 May 2014 17:04, Jaegeuk Kim <jaegeuk.kim@samsung.com> wrote:
> >
> > Hi,
> >
> > 2014-05-04 (일), 23:59 +0000, Paul Ni:
> > > Is it possible to set an arbitrary segment size? I'm trying to set it
> > > to 1.5MiB to make it align with erase blocks on flash chips in my EVO
> > > 840 SSD.
> >
> > Impossible. The hard-coded segment size is fixed to manange the whole FS
> > metadata.
> > If you want to adjust the underlying FTL layout, you can change the
> > section and zone sizes.
> > Thanks,
> >
[...]
> Is there any other way to avoid unaligned writes to erase blocks on
> TLC flash based SSDs? As far as I know, all TLC flash memory has erase
> blocks sizes in multiples of 3.
If you want to align more precisely to the storage, you can configure
the section size in multiples of 3.
For example,
mkfs.f2fs -s 3 $DEV
-> this configures the sections consisting of 3 segments, 6MB.
Thanks,
--
Jaegeuk Kim
Samsung
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2014-05-09 0:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 23:59 Segment size Paul Ni
2014-05-07 0:04 ` Jaegeuk Kim
2014-05-08 19:43 ` Paul Ni
2014-05-09 0:11 ` Jaegeuk Kim [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=1399594316.13268.63.camel@kjgkr \
--to=jaegeuk.kim@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=nikulinpi@gmail.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;
as well as URLs for NNTP newsgroup(s).