All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Qi <joseph.qi@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 0/9 v6] ocfs2: support append O_DIRECT write
Date: Tue, 4 Aug 2015 17:03:54 +0800	[thread overview]
Message-ID: <55C07FFA.4060701@huawei.com> (raw)
In-Reply-To: <55C058D6.9030809@oracle.com>

Hi Ryan,

On 2015/8/4 14:16, Ryan Ding wrote:
> Hi Joseph,
> 
> Sorry for bothering you with the old patches. But I really need to know what this patch is for.
> 
> https://oss.oracle.com/pipermail/ocfs2-devel/2015-January/010496.html
> 
> From above email archive, you mentioned those patches aim to reduce the host page cache consumption. But in my opinion, after append direct io, the page used for buffer is clean. System can realloc those cached pages. We can even call invalidate_mapping_pages to fast that process. Maybe more pages will be needed during direct io. But direct io size can not be too large, right?
> 
We introduced the append direct io because originally ocfs2 would fall
back to buffer io in case of thin provision, which was not the actual
behavior that user expect.
I didn't get you that more pages would be needed during direct io. Could
you please explain it more clearly?

Thanks,
Joseph

> Thanks,
> Ryan
> 
> 

  reply	other threads:[~2015-08-04  9:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04  6:16 [Ocfs2-devel] [PATCH 0/9 v6] ocfs2: support append O_DIRECT write Ryan Ding
2015-08-04  9:03 ` Joseph Qi [this message]
2015-08-05  4:40   ` Ryan Ding
2015-08-05  6:40     ` Joseph Qi
2015-08-05  8:07       ` Ryan Ding
2015-08-05 11:18         ` Joseph Qi
2015-08-06  2:35           ` Ryan Ding
2015-08-05  7:08     ` Joseph Qi
  -- strict thread matches above, loose matches on Subject: below --
2015-01-20  8:01 Joseph Qi
2015-01-20  8:26 ` Junxiao Bi
2015-01-20  9:00   ` Joseph Qi
2015-01-22  2:10     ` Junxiao Bi
2015-01-22  3:54       ` Joseph Qi
2015-01-22  5:06         ` Junxiao Bi

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=55C07FFA.4060701@huawei.com \
    --to=joseph.qi@huawei.com \
    --cc=ocfs2-devel@oss.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 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.