From: Marc Lehmann <schmorp@schmorp.de>
To: Chao Yu <chao2.yu@samsung.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: blog article about f2fs on smr drives
Date: Tue, 17 Nov 2015 00:52:47 +0100 [thread overview]
Message-ID: <20151116235247.GF8583@schmorp.de> (raw)
In-Reply-To: <008401d12027$b15cd700$14168500$@samsung.com>
On Mon, Nov 16, 2015 at 12:31:06PM +0800, Chao Yu <chao2.yu@samsung.com> wrote:
> I think you could get the change information in below link:
>
> http://sourceforge.net/p/linux-f2fs/mailman/message/34427519/
Right, I saw the merge requests, but I don't know if these have been accepted
for 4.3. I assume they are, thanks for finding them again for me.
> > While there are stretches at >>100MB/s, most of the time, this is at less,
> > and often for long stretches at ~10MB/s, which is the reason the end
> > result is (relatively) bad.
>
> Could you please share us IO trace log?
I am already working on it, I just didn't expect it to be a problem. Also,
I did it without your patch.
> > And lastly, is there a document describing the implementation of
> > encryption in the fs, and the goals (privacy? integrity? both?)
>
> The feature was ported from ext4, please refer following article:
>
> https://lwn.net/Articles/639427/
I see, so it inherits all the security issues of that design.
> Actually, as I test in flash device, it does help to improve performance in
> workload of creating nodes aggressively, this is because we add asynchronous
> readahead to mitigate small synchronous random read which may block all APPs
> sometime. Considering rotational device has worse random synchronous read
> performance, I expect better result in SMR.
Ok, that could help, as even a relatively small number of random reads could
cause performance regressions (did the original 3.18 code not yet do this?)
I was a bit confused by the use of SMR, as SMRs don't suffer more from
random reads as othere rotational devices (in fact, they can suffer less,
if the data is still in the journal).
> > Sure, will be happy to do that, what should I tune how? And thanks for
> > working on this!
>
> IMO, one way is to do the test with default value and then do geometrically
> increasing with the value to see how it affects the IO.
I am not sure I can make a large number of tests, I will try to do smaller
tests and see if I can make more of them and see a difference.
Thanks again!
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schmorp@schmorp.de
-=====/_/_//_/\_,_/ /_/\_\
------------------------------------------------------------------------------
Presto, an open source distributed SQL query engine for big data, initially
developed by Facebook, enables you to easily query your data on Hadoop in a
more interactive manner. Teradata is also now providing full enterprise
support for Presto. Download a free open source copy now.
http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140
next prev parent reply other threads:[~2015-11-16 23:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 4:31 blog article about f2fs on smr drives Chao Yu
2015-11-16 23:52 ` Marc Lehmann [this message]
2015-11-17 0:05 ` Jaegeuk Kim
2015-11-17 11:35 ` Chao Yu
-- strict thread matches above, loose matches on Subject: below --
2015-10-08 13:56 Marc Lehmann
2015-10-09 0:45 ` Jaegeuk Kim
2015-11-14 19:21 ` Marc Lehmann
2015-10-19 10:43 ` Chao Yu
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=20151116235247.GF8583@schmorp.de \
--to=schmorp@schmorp.de \
--cc=chao2.yu@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).