linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Xin Zhao <uszhaoxin@gmail.com>
Cc: Dave Kleikamp <shaggy@linux.vnet.ibm.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: Linux page cache issue?
Date: Mon, 2 Apr 2007 14:51:24 +0200	[thread overview]
Message-ID: <20070402125124.GI3728@duck.suse.cz> (raw)
In-Reply-To: <4ae3c140703290741p58199472u3bf9f3f58e4d1db1@mail.gmail.com>

  Hi Xin,

On Thu 29-03-07 10:41:01, Xin Zhao wrote:
> I know we can use device inode's radix tree to achieve the same goal.
> The only downside could be: First, by default, Linux will not add the
> data pages into that radix tree. Only when a file is opened in
  Right.

> O_DIRECT, the data pages will be put into dev's radix tree. Moreover,
  If you use O_DIRECT, I don't think the data will and in any radix tree -
ideally they go directly to disk in this case.

> if the partition is big, I am not sure whether the lookup overhead is
> an issue. So it might need some optimization.
  Maybe, but I'd not say so as my first guess.

> Can you elaborate more about the aliasing issues mentioned in your
> email? I do have some mechanisms to handle the following situation:
> suppose two files share same data blocks. Now two processes open the
> two files separately. If one process writes a file, the other file
> will be affected. Is this the aliasing issue you referred to?
  Yes, this is exactly what I meant. Note that these problems are not
only about writes but also about truncate and such...

								Honza
-- 
Jan Kara <jack@suse.cz>
SuSE CR Labs

      reply	other threads:[~2007-04-02 12:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-28  6:45 Linux page cache issue? Xin Zhao
2007-03-28  7:35 ` junjie cai
2007-03-28  7:38 ` Matthias Kaehlcke
2007-03-28 14:10 ` Dave Kleikamp
2007-03-28 15:39   ` Xin Zhao
     [not found]     ` <alpine.DEB.0.83.0703281157010.2527@sigma.j-a-k-j.com>
2007-03-28 16:15       ` Xin Zhao
2007-03-29  9:27     ` Jan Kara
2007-03-29 14:41       ` Xin Zhao
2007-04-02 12:51         ` Jan Kara [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=20070402125124.GI3728@duck.suse.cz \
    --to=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaggy@linux.vnet.ibm.com \
    --cc=uszhaoxin@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;
as well as URLs for NNTP newsgroup(s).