From: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Vivek Goyal <vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
jstancek-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH 2/2 v2] Add memory usage trace to diffrent hook points
Date: Mon, 14 Jan 2013 16:59:05 +0800 [thread overview]
Message-ID: <50F3C8D9.2020603@redhat.com> (raw)
In-Reply-To: <50EFE2AC.7020704-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On 01/11/2013 06:00 PM, Harald Hoyer wrote:
> Am 11.01.2013 10:05, schrieb Dave Young:
>>
>> Hello harald
>>
>> What's your opinion about this patch? Could you take a look at it?
>>> --- dracut.orig/modules.d/99base/dracut-lib.sh
>>> +++ dracut/modules.d/99base/dracut-lib.sh
>>> @@ -998,3 +998,93 @@ listlist() {
>>> are_lists_eq() {
>>> listlist "$1" "$2" "$3" "$4" && listlist "$1" "$3" "$2" "$4"
>>> }
>>> +
>>> +setmemdebug() {
>>> + if [ -z "$DEBUG_MEM_LEVEL" ]; then
>>> + export DEBUG_MEM_LEVEL=$(getargnum 0 0 3 rd.memdebug)
>>> + fi
>>> +}
>>> +
>>> +setmemdebug
>>> +
>>> +# parameters: msg [trace_level:trace]...
>>> +function make_trace_mem()
>>> +{
>>> + msg=$1
>>> + shift
>>> + if [ "$DEBUG_MEM_LEVEL" -gt 0 ]; then
>>> + make_trace show_memstats $DEBUG_MEM_LEVEL "[debug_mem]" "$msg" "$@"
>>> + fi
>>> +}
>>> +
>>> +# parameters: func log_level prefix msg [trace_level:trace]...
>>> +function make_trace()
>>> +{
>>> + func=$1
>>> + shift
>>> +
>>> + log_level=`echo "$1" | grep -o '^[0-9]\+'`
>
> * use $() instead of ``
Will do
>
>
> * grep is overkill use simple shell functions
>
> There are in modules.d/99base/dracut-lib.sh
> strstr()
> str_starts()
> str_ends()
>
> * or use "case"
>
> case "$1" in
> [0-9]*) log_level=$1;;
> esac
Will do
>
>>> + shift
>>> +
>>> + prefix=$1
>>> + shift
>>> +
>>> + msg=$1
>>> + shift
>>> +
>>> + if [ -z "$log_level" ]; then
>>> + return
>>> + fi
>>> +
>>> + msg=`echo "$msg" | sed 's/^\s\+//'`
>
> sed is overkill for this. Use
> ${var%%...}
> ${var%...}
> ${var#...}
> ${var##...}
>
> $ msg="foo+bar baz"
> $ echo ${msg#*+}
> bar baz
>
Will do
>
>>> +
>>> + msg_printed=0
>>> + while [ $# -gt 0 ]; do
>>> + trace_level=`echo "$1" | grep -o '^[0-9]\+'`
>>> + trace_in_higher_levels=`echo "$1" | grep -o '+'`
>>> + trace=`echo $1 | sed "s/^.*://"`
>
> same same
>
Will do
--
Thanks
Dave
prev parent reply other threads:[~2013-01-14 8:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 2:38 [PATCH 2/2] Add memory usage trace to diffrent hook points Dave Young
[not found] ` <20121126023852.GA6886-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2012-11-27 22:33 ` Vivek Goyal
[not found] ` <20121127223330.GG6964-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-11-28 5:53 ` Dave Young
2012-11-28 8:45 ` [PATCH 2/2 v2] " Dave Young
[not found] ` <50B5CF24.6090006-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-01-11 9:05 ` Dave Young
[not found] ` <50EFD5D8.1070508-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-01-11 10:00 ` Harald Hoyer
[not found] ` <50EFE2AC.7020704-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-01-14 8:59 ` Dave Young [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=50F3C8D9.2020603@redhat.com \
--to=dyoung-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jstancek-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=vgoyal-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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