linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: Alex <hbx7d@yandex.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: Regression in kernel 3.14.0-rc1
Date: Fri, 28 Feb 2014 10:42:14 +0900	[thread overview]
Message-ID: <1393551734.4705.92.camel@kjgkr> (raw)
In-Reply-To: <174911393513364@web17j.yandex.ru>

Hi,

Thank you for the report.

Unfortunately, when I measured dbench in my latest kernel, there was no
regression wrt the patch that you found.

Kernel: 3.14-rc3 with latest f2fs source codes
HW: Intel i5
OS: Ubuntu 12.10 x64
Test: dbench -D /mnt/test -t 6 6 -c ./client.txt

The results showed:
- ext4 : 203 MB/s
- f2fs : 318 MB/s

So, could you share the exact configuration of your dbench?
And, if possible, could you share the numbers of the following tests in
your environment?

1. ext4
2. the latest f2fs from dev branch
3. modified f2fs from the latest f2fs
 : fs/f2fs/file.c
  118      .sync_mode = WB_SYNC_ALL;

4. modified f2fs from the latest f2fs
 : fs/f2fs/node.c
  1221     wbc->sync_mode = WB_SYNC_ALL;

5. modified f2fs with #3 and #4 changes together

Thank you very much. :)
 
2014-02-27 (목), 19:02 +0400, Alex:
> Hello,
> 
> After reading phoronix's f2fs benchmarks http://www.phoronix.com/scan.php?page=article&item=linux_314_ssdfs&num=2 (3rd picture) did kernel bisect and it resulted in this commit https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=fb5566da .
> 
> PS Tried the latest tree from f2fs dev branch with the same results https://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs.git/commit/?h=dev&id=695fd1ed .
> 
> ------------------------------------------------------------------------------
> Flow-based real-time traffic analytics software. Cisco certified tool.
> Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
> Customize your own dashboards, set traffic alerts and generate reports.
> Network behavioral analysis & security monitoring. All-in-one tool.
> http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

-- 
Jaegeuk Kim
Samsung



------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2014-02-28  1:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27 15:02 Regression in kernel 3.14.0-rc1 Alex
2014-02-28  1:42 ` Jaegeuk Kim [this message]
2014-02-28 13:52   ` Alex

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=1393551734.4705.92.camel@kjgkr \
    --to=jaegeuk.kim@samsung.com \
    --cc=hbx7d@yandex.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).