<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-size:small"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Nov 3, 2022 at 5:33 PM Tarun Sahu <<a href="mailto:tsahu@linux.ibm.com" target="_blank">tsahu@linux.ibm.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello, <br>
Thanks for reviewing.<br>
<br>
I am thinking of adding following lines in "lib/hugetlb.h"<br>
<br>
#define HUGEPAGE_TOTAL "HugePages_Total:"<br>
#define HUGEPAGE_FREE "HugePages_Total:"<br>
#define HUGEPAGE_RSVD "HugePages_Total:"<br>
#define HUGEPAGE_Surp "HugePages_Total:"<br>
<br>
There are all test that uses, TOTAL, MANY that uses FREE, few RSVD, SURP.<br>
If we change it now, we can update this series now and, proceed further for<br>
series of next tests.<br>
<br>
What do you think?<br></blockquote><div><br></div><div><div class="gmail_default" style="font-size:small">I guess put in the top header file "inlucde/tst_hugepage.h" should be better,</div><div class="gmail_default" style="font-size:small">it provides more scope(for the whole LTP) of use. </div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">I ever thought to combine this hugetlb/lib there, especially for new cases,</div><div class="gmail_default" style="font-size:small">it would beĀ easier to maintain only one library for hugetlb.</div><div class="gmail_default" style="font-size:small">(and also adding more definitions. e.g. "/proc/sys/vm/nr_overcommit_hugepages")</div></div><div><br></div></div><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div>Regards,<br></div><div>Li Wang<br></div></div></div></div>