d17d8f9ded
We don't have any good way to figure out what kinds of flushes are being attempted. Right now, we can try to use the vm counters, but those only tell us what we actually did with the hardware (one-by-one vs full) and don't tell us what was actually _requested_. This allows us to select out "interesting" TLB flushes that we might want to optimize (like the ranged ones) and ignore the ones that we have very little control over (the ones at context switch). Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com> Link: http://lkml.kernel.org/r/20140731154059.4C96CBA5@viggo.jf.intel.com Acked-by: Rik van Riel <riel@redhat.com> Cc: Mel Gorman <mgorman@suse.de> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com> |
||
|---|---|---|
| .. | ||
| 9p.h | ||
| asoc.h | ||
| bcache.h | ||
| block.h | ||
| btrfs.h | ||
| compaction.h | ||
| context_tracking.h | ||
| ext3.h | ||
| ext4.h | ||
| f2fs.h | ||
| filelock.h | ||
| filemap.h | ||
| gfpflags.h | ||
| gpio.h | ||
| host1x.h | ||
| hswadsp.h | ||
| i2c.h | ||
| intel-sst.h | ||
| iommu.h | ||
| irq.h | ||
| jbd2.h | ||
| jbd.h | ||
| kmem.h | ||
| kvm.h | ||
| lock.h | ||
| mce.h | ||
| migrate.h | ||
| module.h | ||
| napi.h | ||
| net.h | ||
| nmi.h | ||
| oom.h | ||
| pagemap.h | ||
| power_cpu_migrate.h | ||
| power.h | ||
| printk.h | ||
| random.h | ||
| ras.h | ||
| rcu.h | ||
| regmap.h | ||
| regulator.h | ||
| rpm.h | ||
| sched.h | ||
| scsi.h | ||
| signal.h | ||
| skb.h | ||
| sock.h | ||
| spi.h | ||
| sunrpc.h | ||
| swiotlb.h | ||
| syscalls.h | ||
| target.h | ||
| task.h | ||
| timer.h | ||
| tlb.h | ||
| udp.h | ||
| v4l2.h | ||
| vmscan.h | ||
| workqueue.h | ||
| writeback.h | ||
| xen.h | ||