From: Jens Axboe <axboe@kernel.dk>
To: Zhang Taile <zhangtl@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: memory leak bug? when do write with verify
Date: Thu, 15 Sep 2011 09:24:28 +0200 [thread overview]
Message-ID: <4E71A82C.5050507@kernel.dk> (raw)
In-Reply-To: <CADson1y9VBx_gvHHafaQddA9NHjpwFwgtWZ854HHGE+EgfBvZw@mail.gmail.com>
On 2011-09-15 04:49, Zhang Taile wrote:
> Hi ,
> Understand now.
> One more question, what backlog for? Why read only with verify do not
> need it?
It's not strictly necessary for most cases. For random writes, we can
verify faster by doing it in disk order instead of in write order. If
you are using trim to discard parts of the ranges, then we need those
appropriately marked in memory.
But we can/could relax it a bit and save the memory. I don't think I've
had this complaint before, I guess people generally have plenty of RAM
these days :-)
--
Jens Axboe
prev parent reply other threads:[~2011-09-15 7:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADson1wk9astwdroeAtPXb4A3+yrAcDcCXaEPvEGJPhM4TBfqQ@mail.gmail.com>
2011-09-14 9:53 ` memory leak bug? when do write with verify Zhang Taile
2011-09-14 9:56 ` Jiri Horky
2011-09-14 13:13 ` Zhang Taile
2011-09-14 17:39 ` Jens Axboe
2011-09-15 2:49 ` Zhang Taile
2011-09-15 7:24 ` Jens Axboe [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=4E71A82C.5050507@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=zhangtl@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox