From: Cyril Hrubis <chrubis@suse.cz>
To: Tarun Sahu <tsahu@linux.ibm.com>
Cc: sbhat@linux.ibm.com, aneesh.kumar@linux.ibm.com,
geetika@linux.ibm.com, vaibhav@linux.ibm.com,
rpalethorpe@suse.com, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v7 3/4] Hugetlb: Migrating libhugetlbfs chunk-overcommit
Date: Fri, 4 Nov 2022 14:19:53 +0100 [thread overview]
Message-ID: <Y2UReVDcsxQctNYu@yuki> (raw)
In-Reply-To: <20221104131615.dac6oo3tt2f56xi3@tarunpc>
Hi!
> > #define HUGEFILE MNTPOINT "hugefile"
> >
> > ...
> > huge_fd = tst_creat_unlinked(HUGEFILE);
> > ...
> >
> This function creat a file with random name, so that one test
> can call this function multiple times to creat multple files
> whenever required. So it will just take the path inside which it will creat
> all these files. To keep hugetlb test file with ditinguisable name, the path
> is sufficient, no need to take hugefile as argument.
>
> So file is: hugetlbfs/ltp_xxxxxx_<tid>
Sorry, I got somehow confused in the morning, of course the code is
correct.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-11-04 13:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 6:27 [LTP] [PATCH v7 0/4] Hugetlb:Migrating the libhugetlbfs tests Tarun Sahu
2022-11-04 6:27 ` [LTP] [PATCH v7 1/4] Hugetlb: Add new tst_test options for hugeltb test support Tarun Sahu
2022-11-04 6:27 ` [LTP] [PATCH v7 2/4] Hugetlb: Migrating libhugetlbfs brk_near_huge Tarun Sahu
2022-11-04 9:21 ` Cyril Hrubis
2022-11-04 6:27 ` [LTP] [PATCH v7 3/4] Hugetlb: Migrating libhugetlbfs chunk-overcommit Tarun Sahu
2022-11-04 9:36 ` Cyril Hrubis
2022-11-04 13:16 ` Tarun Sahu
2022-11-04 13:19 ` Cyril Hrubis [this message]
2022-11-04 6:27 ` [LTP] [PATCH v7 4/4] Hugetlb: Migrating libhugetlbfs corrupt-by-cow-opt Tarun Sahu
2022-11-04 9:51 ` Cyril Hrubis
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=Y2UReVDcsxQctNYu@yuki \
--to=chrubis@suse.cz \
--cc=aneesh.kumar@linux.ibm.com \
--cc=geetika@linux.ibm.com \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.com \
--cc=sbhat@linux.ibm.com \
--cc=tsahu@linux.ibm.com \
--cc=vaibhav@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox