summaryrefslogtreecommitdiff
path: root/ipc/msgutil.c
diff options
context:
space:
mode:
authorRoland Dreier <roland@purestorage.com>2014-05-02 11:18:41 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2014-07-17 15:58:04 -0700
commitb0d9e0106fc25de7491dfddde9729ea220dfd8df (patch)
tree2ce12e3e3aef56e03e9e0b8cfa8c6685c972725b /ipc/msgutil.c
parenta2f37ebbc94130e1299287e8601c0d27cf59cee5 (diff)
downloadlinux-3.10-b0d9e0106fc25de7491dfddde9729ea220dfd8df.tar.gz
linux-3.10-b0d9e0106fc25de7491dfddde9729ea220dfd8df.tar.bz2
linux-3.10-b0d9e0106fc25de7491dfddde9729ea220dfd8df.zip
x86, ioremap: Speed up check for RAM pages
commit c81c8a1eeede61e92a15103748c23d100880cc8a upstream. In __ioremap_caller() (the guts of ioremap), we loop over the range of pfns being remapped and checks each one individually with page_is_ram(). For large ioremaps, this can be very slow. For example, we have a device with a 256 GiB PCI BAR, and ioremapping this BAR can take 20+ seconds -- sometimes long enough to trigger the soft lockup detector! Internally, page_is_ram() calls walk_system_ram_range() on a single page. Instead, we can make a single call to walk_system_ram_range() from __ioremap_caller(), and do our further checks only for any RAM pages that we find. For the common case of MMIO, this saves an enormous amount of work, since the range being ioremapped doesn't intersect system RAM at all. With this change, ioremap on our 256 GiB BAR takes less than 1 second. Signed-off-by: Roland Dreier <roland@purestorage.com> Link: http://lkml.kernel.org/r/1399054721-1331-1-git-send-email-roland@kernel.org Signed-off-by: H. Peter Anvin <hpa@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'ipc/msgutil.c')
0 files changed, 0 insertions, 0 deletions