All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	Namjae Jeon <namjae.jeon@samsung.com>,
	Vivek Trivedi <t.vivek@samsung.com>
Subject: Re: [PATCH 1/2] writeback: add dirty_background_time per bdi variable
Date: Wed, 12 Sep 2012 07:25:37 +0800	[thread overview]
Message-ID: <20120911232537.GA13210@localhost> (raw)
In-Reply-To: <CAKYAXd_Zdb_3rqwgf03To+DPw-wFXUGW-5km7KVaiJSymEuGMg@mail.gmail.com>

On Wed, Sep 12, 2012 at 08:12:40AM +0900, Namjae Jeon wrote:
> >>
> >> To be frank, no realistic NFS servers will use USB disk as backing
> >> storage. So that rational for reducing "initial" delays is weak.
> >> Continuous write performance to HDD is much more important. Do you
> >> have numbers for that?
> >
> > Actually, we use USB HDD and USB Flash devices at NFS server.
> > There can be other similar users as well. So it might be useful to
> > provide this tuning feature other.
> > As default value is zero, it is disabled by default and it should not
> > impact normal writeback.
> >
> > I will share large file writes test result on NFS client on USB HDD
> > with/without tuning with patch.
> Hi. Wu.
> I share 1GB continous write test result.
> 
> -> create a 1000 MB file
> For continuous write - create 1 GB file
> 
>  RecSize   WriteSpeed
> 10485760   10.47MB/sec
>  1048576   10.35MB/sec
>   524288   10.48MB/sec
>   262144   10.48MB/sec
>   131072   10.52MB/sec
>    65536   10.56MB/sec
>    32768   10.64MB/sec
>    16384   10.31MB/sec
>     8192   10.52MB/sec
>     4096   10.45MB/sec
> 
> I will update changelog in patch.

Thanks! What's the server side setting and can you give a comparison
of different background writeback thresholds? This is this patch's
target use cases, after all.

Thanks,
Fengguang

  reply	other threads:[~2012-09-11 23:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-27 16:01 [PATCH 1/2] writeback: add dirty_background_time per bdi variable Namjae Jeon
2012-09-11  1:40 ` Fengguang Wu
2012-09-11  5:03   ` Namjae Jeon
2012-09-11 23:12     ` Namjae Jeon
2012-09-11 23:25       ` Fengguang Wu [this message]
2012-09-11 23:43         ` Namjae Jeon
2012-09-12  6:04           ` Namjae Jeon
2012-09-12  6:10             ` Fengguang Wu
2012-09-12 17:01 ` Aneesh Kumar K.V

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=20120911232537.GA13210@localhost \
    --to=fengguang.wu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=linkinjeon@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namjae.jeon@samsung.com \
    --cc=t.vivek@samsung.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.