From: Christoph Hellwig <hch@infradead.org>
To: Waiman Long <Waiman.Long@hpe.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Scott J Norton <scott.norton@hpe.com>,
Douglas Hatch <doug.hatch@hpe.com>
Subject: Re: [RFC PATCH] ext4: Don't release mutex for DAX write
Date: Tue, 3 May 2016 01:43:43 -0700 [thread overview]
Message-ID: <20160503084343.GA31363@infradead.org> (raw)
In-Reply-To: <1462219138-44089-1-git-send-email-Waiman.Long@hpe.com>
As explained in another thread I really think we need to get DAX
to stop pretending to be direct I/O, which should also take care
of the locking. The same issue also exists for ext2 and XFS so it
needs to be solved at a higher level.
next prev parent reply other threads:[~2016-05-03 8:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 19:58 [RFC PATCH] ext4: Don't release mutex for DAX write Waiman Long
2016-05-03 8:43 ` Christoph Hellwig [this message]
2016-05-03 15:58 ` Waiman Long
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=20160503084343.GA31363@infradead.org \
--to=hch@infradead.org \
--cc=Waiman.Long@hpe.com \
--cc=adilger.kernel@dilger.ca \
--cc=doug.hatch@hpe.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.norton@hpe.com \
--cc=tytso@mit.edu \
/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