linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jianshen Liu <ljishen@gmail.com>
To: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Question: Modifying kernel to handle all I/O requests without page cache
Date: Wed, 25 Sep 2019 15:51:27 -0700	[thread overview]
Message-ID: <CAMgD0BoT82ApOQ=Fk6o5KYMsC=z7M88zkNCw9XuMtB0y-xaAmw@mail.gmail.com> (raw)

Hi,

I am working on a project trying to evaluate the performance of a
workload running on a storage device. I don't want the benchmark
result depends on a specific platform (e.g., a platform with X GiB of
physical memory). Because it prevents people from reproducing the same
result on a different platform configuration. Think about you are
benchmarking a read-heavy workload, with data caching enabled you may
end up with just testing the performance of the system memory.

Currently, I'm thinking how to eliminate the cache effects created by
the page cache. Direct I/O is a good option for testing with a single
application but is not good for testing with unknown
applications/workloads. Therefore, it is not feasible to ask people to
modify the application source code before running the benchmark.

Making changes within the kernel may only be the option because it is
transparent to all user-space applications. The problem is I don't
know how to modify the kernel so that it does not use the page cache
for any IOs to a specific storage device. I have tried to append a
fadvise64() call with POSIX_FADV_DONTNEED to the end of each
read/write system calls. The performance of this approach is far from
using Direct I/O. It is also unable to eliminate the caching effects
under concurrent I/Os. I'm looking for any advice here to point me an
efficient way to remove the cache effects from the page cache.

Thanks,
Jianshen

             reply	other threads:[~2019-09-25 22:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25 22:51 Jianshen Liu [this message]
2019-09-26 12:39 ` Question: Modifying kernel to handle all I/O requests without page cache Carlos Maiolino
2019-09-27  1:42   ` Jianshen Liu
2019-09-27 10:39     ` Carlos Maiolino
2019-09-27 22:17     ` Dave Chinner

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='CAMgD0BoT82ApOQ=Fk6o5KYMsC=z7M88zkNCw9XuMtB0y-xaAmw@mail.gmail.com' \
    --to=ljishen@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.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).