linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Fasheh <mark.fasheh@oracle.com>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: what happened to RELATIME?
Date: Mon, 3 Dec 2007 13:34:06 -0800	[thread overview]
Message-ID: <20071203213406.GJ28607@ca-server1.us.oracle.com> (raw)
In-Reply-To: <056a01c835e9$5b7203f0$5267a8c0@Jocke>

On Mon, Dec 03, 2007 at 09:16:15PM +0100, Joakim Tjernlund wrote:
> Looking in 2.6.23 sources it seems like only ocfs2 has added
> support for RELATIME. Was RELATIME a bad idea or is there
> some other reason other filesystems hasn't added support?

Ocfs2 just needs a bit of explicit support - as far as I recall, other file
systems should have gotten it automagically via the generic vfs changes.
	--Mark

--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com

  reply	other threads:[~2007-12-03 21:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-03 20:16 what happened to RELATIME? Joakim Tjernlund
2007-12-03 21:34 ` Mark Fasheh [this message]
2007-12-03 23:46   ` Joakim Tjernlund

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=20071203213406.GJ28607@ca-server1.us.oracle.com \
    --to=mark.fasheh@oracle.com \
    --cc=joakim.tjernlund@transmode.se \
    --cc=linux-kernel@vger.kernel.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).