All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-fsdevel@vger.kernel.org, linux-nvdimm@lists.01.org
Subject: fs_dax_get_by_host in the hot path
Date: Thu, 24 Aug 2017 15:45:00 +0200	[thread overview]
Message-ID: <20170824134500.GA25037@lst.de> (raw)

Hi Dan,

I just noticed that we now do a fs_dax_get_by_host in every
iomap_begin call for DAX.  This function iterates a list,
does a string compared and igrab.  I really think we need
to cache this in the superblock (possible even the fs
superblock) similar to what we do for the block device.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-nvdimm@lists.01.org, linux-fsdevel@vger.kernel.org
Subject: fs_dax_get_by_host in the hot path
Date: Thu, 24 Aug 2017 15:45:00 +0200	[thread overview]
Message-ID: <20170824134500.GA25037@lst.de> (raw)

Hi Dan,

I just noticed that we now do a fs_dax_get_by_host in every
iomap_begin call for DAX.  This function iterates a list,
does a string compared and igrab.  I really think we need
to cache this in the superblock (possible even the fs
superblock) similar to what we do for the block device.

             reply	other threads:[~2017-08-24 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24 13:45 Christoph Hellwig [this message]
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 14:48   ` Dan Williams
2017-08-24 15:19   ` Christoph Hellwig
2017-08-24 15:19     ` Christoph Hellwig

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=20170824134500.GA25037@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 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.