All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <dchinner@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Interest in DAX for OCFS2 and/or GFS2?
Date: Fri, 18 Oct 2019 07:33:12 +1100	[thread overview]
Message-ID: <20191017203312.GK25485@rh> (raw)
In-Reply-To: <AT5PR8401MB1025DFAE60F5A5A4BCC5D2038B940@AT5PR8401MB1025.NAMPRD84.PROD.OUTLOOK.COM>

On Thu, Oct 10, 2019 at 04:41:56PM +0000, Hayes, Bill wrote:
> Has there been any discussion or interest in DAX support in OCFS2?
> Is there interest from the OCFS2 development community to see DAX support developed and put upstream?
> 
> Has there been any discussion or interest in DAX support in GFS2?
> Is there interest from the GFS2 development community to see DAX support developed and put upstream?

You're probably best from a DAX implementation POV to head down the
GFS2 path, as FS-DAX requires the filesystem to use the fs/iomap/
extent mapping implementation. GFS2 is already partially ported to
use the iomap infrastructure, though more work is needed to provide
the iomap functionality DAX requires. OCFS2 would require a lot more
work on this front....

Cheers,

Dave.
-- 
Dave Chinner
dchinner at redhat.com



      parent reply	other threads:[~2019-10-17 20:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-10 16:41 [Cluster-devel] Interest in DAX for OCFS2 and/or GFS2? Hayes, Bill
2019-10-11  7:21 ` [Ocfs2-devel] " Gang He
2019-10-11  7:21   ` [Cluster-devel] " Gang He
2019-10-11 10:14   ` [Ocfs2-devel] " Steven Whitehouse
2019-10-11 10:14     ` Steven Whitehouse
2019-10-17 20:33 ` Dave Chinner [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=20191017203312.GK25485@rh \
    --to=dchinner@redhat.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.