All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Don Zickus <dzickus@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: perf: thread is its own parent
Date: Thu, 19 Mar 2015 07:56:32 -0600	[thread overview]
Message-ID: <550AD590.9090904@gmail.com> (raw)
In-Reply-To: <20150319132048.GB162412@redhat.com>

On 3/19/15 7:20 AM, Don Zickus wrote:
> Honestly I don't recall.   The commit log tells you the problem I was trying
> to solve.  Instead of parsing text strings from/proc/maps/<pid>, I believe
> it was waaaay faster to copy the thread maps.
>
> This could have been an oversight.  I might have falsely assumed tgid ==
> ppid?
>
> Are you finding a problem with it?


rebasing my scheduling timehist command to 4.0 and this change breaks 
one of the options. If there are no objections I'll send a patch along 
with others to set ptid and ppid to -1 (that's what it is in 3.12).

Thanks,
David

  reply	other threads:[~2015-03-19 13:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18 23:56 perf: thread is its own parent David Ahern
2015-03-19 13:20 ` Don Zickus
2015-03-19 13:56   ` David Ahern [this message]
2015-03-19 14:27     ` Don Zickus

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=550AD590.9090904@gmail.com \
    --to=dsahern@gmail.com \
    --cc=acme@kernel.org \
    --cc=dzickus@redhat.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.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 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.