From: Mark Fasheh <mark.fasheh@oracle.com>
To: Steven Whitehouse <steve@chygwyn.com>
Cc: Valerie Henson <val_henson@linux.intel.com>,
linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Re: What's in ocfs2.git
Date: Mon Dec 4 16:10:12 2006 [thread overview]
Message-ID: <20061205001007.GF19617@ca-server1.us.oracle.com> (raw)
In-Reply-To: <1165229693.3752.629.camel@quoit.chygwyn.com>
Hi Steve,
On Mon, Dec 04, 2006 at 10:54:53AM +0000, Steven Whitehouse wrote:
> > In the future, I'd like to see a "relative atime" mode, which functions
> > in the manner described by Valerie Henson at:
> >
> > http://lkml.org/lkml/2006/8/25/380
> >
> I'd like to second that. [adding Val Henson to the "to"] What (if
> anything) remains to be done before the relative atime patch is ready to
> go upstream? I'm happy to help out here if required,
Last time I looked at them, things seemed to be in pretty good shape - it
wasn't a very large patch series.
The thing is (I'm going from memory here), gfs2 and ocfs2 are likely to just
make use of the option parsing (and setting of the MNT_RELATIME flag), and
ignore the changes to touch_atime() since we we handle our own atime
updates.
Overall I think it's a matter of pushing the patches to the kernel and to
mount(8). For ocfs2/gfs2 we implement a small amount of the logic in our
"lock and update atime" functions.
--Mark
--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com
WARNING: multiple messages have this Message-ID (diff)
From: Mark Fasheh <mark.fasheh@oracle.com>
To: Steven Whitehouse <steve@chygwyn.com>
Cc: Valerie Henson <val_henson@linux.intel.com>,
linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: Re: What's in ocfs2.git
Date: Mon, 4 Dec 2006 16:10:07 -0800 [thread overview]
Message-ID: <20061205001007.GF19617@ca-server1.us.oracle.com> (raw)
In-Reply-To: <1165229693.3752.629.camel@quoit.chygwyn.com>
Hi Steve,
On Mon, Dec 04, 2006 at 10:54:53AM +0000, Steven Whitehouse wrote:
> > In the future, I'd like to see a "relative atime" mode, which functions
> > in the manner described by Valerie Henson at:
> >
> > http://lkml.org/lkml/2006/8/25/380
> >
> I'd like to second that. [adding Val Henson to the "to"] What (if
> anything) remains to be done before the relative atime patch is ready to
> go upstream? I'm happy to help out here if required,
Last time I looked at them, things seemed to be in pretty good shape - it
wasn't a very large patch series.
The thing is (I'm going from memory here), gfs2 and ocfs2 are likely to just
make use of the option parsing (and setting of the MNT_RELATIME flag), and
ignore the changes to touch_atime() since we we handle our own atime
updates.
Overall I think it's a matter of pushing the patches to the kernel and to
mount(8). For ocfs2/gfs2 we implement a small amount of the logic in our
"lock and update atime" functions.
--Mark
--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com
next prev parent reply other threads:[~2006-12-04 16:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-03 12:31 [Ocfs2-devel] What's in ocfs2.git Mark Fasheh
2006-12-03 20:31 ` Mark Fasheh
2006-12-04 10:54 ` Steven Whitehouse
2006-12-04 16:10 ` Mark Fasheh [this message]
2006-12-05 0:10 ` Mark Fasheh
2006-12-05 0:36 ` Relative atime (was Re: What's in ocfs2.git) Valerie Henson
2006-12-05 0:56 ` Valerie Henson
2006-12-05 14:20 ` [Ocfs2-devel] " Mark Fasheh
2006-12-05 22:20 ` Mark Fasheh
2006-12-05 22:12 ` [Ocfs2-devel] " Andrew Morton
2006-12-06 6:11 ` Andrew Morton
2006-12-05 20:58 ` [Ocfs2-devel] " Andrew Morton
2006-12-06 4:58 ` Andrew Morton
2006-12-06 8:58 ` Valerie Henson
2006-12-06 9:42 ` Eric Dumazet
2006-12-06 9:42 ` Eric Dumazet
2006-12-06 12:48 ` Arjan van de Ven
2006-12-09 3:15 ` Valerie Henson
2006-12-12 9:30 ` Karel Zak
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=20061205001007.GF19617@ca-server1.us.oracle.com \
--to=mark.fasheh@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=steve@chygwyn.com \
--cc=val_henson@linux.intel.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.