From: Christoph Hellwig <hch@lst.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Christoph Hellwig <hch@lst.de>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: fs_dax_get_by_host in the hot path
Date: Thu, 24 Aug 2017 17:19:06 +0200 [thread overview]
Message-ID: <20170824151906.GA26646@lst.de> (raw)
In-Reply-To: <CAPcyv4iuSJ5NFt4dLKWm9gemgKm3WggpFWoMFmbCq8wAKVN6+A@mail.gmail.com>
On Thu, Aug 24, 2017 at 07:48:18AM -0700, Dan Williams wrote:
> Sure, I'll get that fixed up. I believe I arrived at this scheme as a
> side-effect / misunderstanding of this comment:
>
> https://groups.google.com/d/msg/linux.kernel/9ho8SFe6RSw/6zTgNaNTCgAJ
The current scheme is doing the right thing in terms of returning
the dax device from ->iomap_begin. But it still do so efficiently :)
prev parent reply other threads:[~2017-08-24 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 13:45 fs_dax_get_by_host in the hot path Christoph Hellwig
2017-08-24 14:48 ` Dan Williams
2017-08-24 15:19 ` Christoph Hellwig [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=20170824151906.GA26646@lst.de \
--to=hch@lst.de \
--cc=dan.j.williams@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.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).