From: Zheng Liu <gnehzuil.liu@gmail.com>
To: Sunil Mushran <sunil.mushran@oracle.com>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [RFC] fadvise: add more flags to provide a hint for block allocation
Date: Tue, 6 Mar 2012 21:30:55 +0800 [thread overview]
Message-ID: <20120306133054.GA24695@gmail.com> (raw)
In-Reply-To: <4F5591DB.4060807@oracle.com>
On Mon, Mar 05, 2012 at 08:26:03PM -0800, Sunil Mushran wrote:
> On 3/5/2012 6:35 PM, Zheng Liu wrote:
> >No, _RANDOM means that file system doesn't need to try its best to find
> >a proper position to allocate some blocks for this file. Furthermore,
> >currently random IOs seem that they are not obviously slower than
> >sequential IOs in Flash/SSD device. For example, when users know a file
> >that is accessed infrequently, they can put this file in a corner, such
> >as in some discontinuously blocks. Then sequential blocks are reserved
> >for the file that needs to be accessed frequently and users can obtain
> >the better performance.
>
> Then FADV_ALLOC_HOT_REGION and FADV_ALLOC_COLD_REGION are
> probably better terms.
Make sense to me. Thanks a lot. ;-)
Regards,
Zheng
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-03-06 13:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 12:50 [RFC] fadvise: add more flags to provide a hint for block allocation Zheng Liu
2012-03-05 19:48 ` Sunil Mushran
2012-03-06 2:35 ` Zheng Liu
2012-03-06 4:26 ` Sunil Mushran
2012-03-06 13:30 ` Zheng Liu [this message]
2012-03-06 8:27 ` Lukas Czerner
2012-03-06 13:56 ` Zheng Liu
2012-03-06 14:29 ` Lukas Czerner
2012-03-06 17:53 ` Sunil Mushran
2012-03-07 8:51 ` Lukas Czerner
2012-03-07 17:11 ` Ted Ts'o
2012-03-07 0:51 ` Dave Chinner
2012-03-07 4:14 ` Andreas Dilger
2012-03-07 5:02 ` Martin K. Petersen
2012-03-07 12:11 ` Dave Chinner
2012-03-08 4:23 ` Martin K. Petersen
2012-03-08 7:07 ` Dave Chinner
2012-03-08 17:01 ` Martin K. Petersen
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=20120306133054.GA24695@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sunil.mushran@oracle.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;
as well as URLs for NNTP newsgroup(s).