All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Gautam Menghani <gautammenghani201@gmail.com>
Cc: damon@lists.linux.dev
Subject: Re: Question about hugetlbfs tests
Date: Tue, 16 Aug 2022 20:50:30 +0000	[thread overview]
Message-ID: <20220816205030.96988-1-sj@kernel.org> (raw)
In-Reply-To: <YvvLo7wDBA6qL0L9@biggie>

Hi Gautam,

On Tue, 16 Aug 2022 22:23:55 +0530 Gautam Menghani <gautammenghani201@gmail.com> wrote:

> Hi,
> 
> I have been looking to understand the TODO mentioned in the damon-tests repo
> on github here: https://github.com/awslabs/damon-tests/tree/master/corr
> 
> The TODO in corr/TODO says "Test hugetlbfs". I want to understand what is
> required in this.

Thank you very much for showing your interest in the TODO item!

> Do we need a test that writes data to hugepages and reads it back to check if
> read/write is successful?
> Or do we need a hugepage scheme that is applied on masim, which we then check
> to ensure hugepages were used?

I'd prefer this option.  That is, making 'masim' to support use of hugetlbfs
and checking if DAMON still monitors the access pattern well, maybe by
extending masim-record test[1].

> Or is something else required?
> Please advise on this.

No problem, hope the above answer be some help.  If there is anything unclear
or I'm wrong, please let me know.

And, now I remember that you already sent me this question via github[2], and I
was totally missing that.  Please forgive my dullness.  I was in vacation at
that time, so I wanted to answer as soon as return from vacation, but I was
forgetting till now.  Sorry again.

[1] https://github.com/awslabs/damon-tests/blob/master/corr/tests/masim-record.sh
[2] https://github.com/awslabs/damon-tests/issues/1


Thanks,
SJ

> 
> Thanks,
> Gautam

      reply	other threads:[~2022-08-16 20:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 16:53 Question about hugetlbfs tests Gautam Menghani
2022-08-16 20:50 ` SeongJae Park [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=20220816205030.96988-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=damon@lists.linux.dev \
    --cc=gautammenghani201@gmail.com \
    /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.