All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xiubo Li <lixiubo@cmss.chinamobile.com>
To: Mike Christie <mchristi@redhat.com>,
	Andy Grover <agrover@redhat.com>,
	nab@linux-iscsi.org, shli@kernel.org
Cc: hch@lst.de, sheng@yasker.org, namei.unix@gmail.com,
	bart.vanassche@sandisk.com, linux-scsi@vger.kernel.org,
	target-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jianfei Hu <hujianfei@cmss.chinamobile.com>,
	Venky Shankar <vshankar@redhat.com>
Subject: Re: [PATCH] target/user: Add daynmic growing data area featuresupport
Date: Wed, 1 Mar 2017 09:22:32 +0800	[thread overview]
Message-ID: <6a938be6-1ca6-ccb2-2fbe-c5fd323ce8bb@cmss.chinamobile.com> (raw)
In-Reply-To: <58B5BDC2.3040300@redhat.com>


>>> Write throughput is pretty
>>> low at around 150 MB/s.
>> What's the original write throughput without this patch? Is it also
>> around 80 MB/s ?
> It is around 20-30 MB/s. Same fio args except using --rw=write.
Got it.

Thanks.

BRs
Xiubo

  reply	other threads:[~2017-03-01  1:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17  9:24 [PATCH] target/user: Add daynmic growing data area feature support lixiubo
2017-02-22 20:32 ` Andy Grover
2017-02-24  2:07   ` [PATCH] target/user: Add daynmic growing data area featuresupport Xiubo Li
2017-02-24 22:29     ` Andy Grover
2017-02-27  5:59       ` Xiubo Li
2017-02-27 19:32         ` how to unmap pages in an anonymous mmap? Andy Grover
2017-02-27 19:32           ` Andy Grover
2017-03-10  1:45           ` Xiubo Li
2017-03-10  1:45             ` Xiubo Li
2017-03-10  1:45             ` Xiubo Li
2017-02-27 23:56   ` [PATCH] target/user: Add daynmic growing data area feature support Mike Christie
2017-02-28  1:22     ` [PATCH] target/user: Add daynmic growing data area featuresupport Xiubo Li
2017-02-28 18:13       ` Mike Christie
2017-03-01  1:22         ` Xiubo Li [this message]
2017-02-28  9:13     ` Xiubo Li
2017-03-01 10:53   ` Xiubo Li

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=6a938be6-1ca6-ccb2-2fbe-c5fd323ce8bb@cmss.chinamobile.com \
    --to=lixiubo@cmss.chinamobile.com \
    --cc=agrover@redhat.com \
    --cc=bart.vanassche@sandisk.com \
    --cc=hch@lst.de \
    --cc=hujianfei@cmss.chinamobile.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mchristi@redhat.com \
    --cc=nab@linux-iscsi.org \
    --cc=namei.unix@gmail.com \
    --cc=sheng@yasker.org \
    --cc=shli@kernel.org \
    --cc=target-devel@vger.kernel.org \
    --cc=vshankar@redhat.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.