From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Randy Dunlap <rdunlap@infradead.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Johannes Thumshirn <jth@kernel.org>,
Naohiro Aota <Naohiro.Aota@wdc.com>,
"Darrick J . Wong" <darrick.wong@oracle.com>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH v6 2/2] zonefs: Add documentation
Date: Wed, 15 Jan 2020 06:23:21 +0000 [thread overview]
Message-ID: <BYAPR04MB5816BB7B5946E4E8643F9DC3E7370@BYAPR04MB5816.namprd04.prod.outlook.com> (raw)
In-Reply-To: c9f37661-03a0-22e3-4b99-b97c47917b5d@infradead.org
Randy,
On 2020/01/15 3:25, Randy Dunlap wrote:
> Hi Damien,
>
> Here are a few editorial comments for you...
Thanks ! All fixed.
[...]
>> +For sequential write zone files, the file size changes as data is appended at
>> +the end of the file, similarly to any regular file system.
>> +
>> +# dd if=/dev/zero of=/mnt/seq/0 bs=4096 count=1 conv=notrunc oflag=direct
>> +1+0 records in
>> +1+0 records out
>> +4096 bytes (4.1 kB, 4.0 KiB) copied, 1.05112 s, 3.9 kB/s
>
> Still slow. You don't want to change that?
Good catch. I thought I had fixed that. Here is the updated dd run,
after making sure that the disk has woken up from low power state before
running:
dd if=/dev/zero of=/mnt/seq/0 bs=4096 count=1 conv=notrunc oflag=direct
1+0 records in
1+0 records out
4096 bytes (4.1 kB, 4.0 KiB) copied, 0.00044121 s, 9.3 MB/s
The HDD write cache is on and empty at the time of running this, which
explains the much lower I/O time.
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2020-01-15 6:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 8:36 [PATCH v6 0/2] New zonefs file system Damien Le Moal
2020-01-08 8:36 ` [PATCH v6 1/2] fs: " Damien Le Moal
2020-01-09 20:17 ` Darrick J. Wong
2020-01-14 9:04 ` Johannes Thumshirn
2020-01-08 8:36 ` [PATCH v6 2/2] zonefs: Add documentation Damien Le Moal
2020-01-14 9:06 ` Johannes Thumshirn
2020-01-14 18:24 ` Randy Dunlap
2020-01-15 6:23 ` Damien Le Moal [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=BYAPR04MB5816BB7B5946E4E8643F9DC3E7370@BYAPR04MB5816.namprd04.prod.outlook.com \
--to=damien.lemoal@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=darrick.wong@oracle.com \
--cc=hare@suse.de \
--cc=jth@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=torvalds@linux-foundation.org \
/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).