public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Li Wang <liwang@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] lib: add tst_read_meminfo / tst_get_avail_mem
Date: Wed, 13 Jul 2016 17:35:05 +0800	[thread overview]
Message-ID: <20160713093505.GA6033@gmail.com> (raw)
In-Reply-To: <1809783770.6955910.1466060898915.JavaMail.zimbra@redhat.com>

Jan,

On Thu, Jun 16, 2016 at 03:08:18AM -0400, Jan Stancek wrote:
> 
> I'm now considering exposing just a parse function, I'd like to
> avoid having separate function for each proc file. And possibly
> more than one since those 2 proc files you mentioned don't have
> uniform format for all content.

How is the parse function going?

As there comes more and more places need get_mem_avaliable(), my opinion
is that we can apply your walk_file_lines() patch first, and let the
/proc/meminfo could be read by this lib. Then if we need more proc/files info
in future, adding new separate function is also accepted.

After all, we had discussed that one parse function for each proc file
is very hard to achive.

Regards,
Li Wang

  parent reply	other threads:[~2016-07-13  9:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14 11:27 [LTP] [PATCH] lib: add tst_read_meminfo / tst_get_avail_mem Jan Stancek
2016-06-14 14:37 ` Li Wang
2016-06-15  7:34   ` Jan Stancek
2016-06-15 12:51     ` Jan Stancek
2016-06-16  5:25       ` Li Wang
2016-06-16  7:08         ` Jan Stancek
2016-06-16  7:32           ` Li Wang
2016-07-13  9:35           ` Li Wang [this message]
2016-07-13 13:12             ` Jan Stancek
2016-07-13 13:54               ` Cyril Hrubis
2016-07-13 14:13                 ` Jan Stancek
2016-07-13 14:23                   ` Cyril Hrubis
2016-07-14  8:03               ` Li Wang

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=20160713093505.GA6033@gmail.com \
    --to=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    /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