[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <37D7C6CF3E00A74B8858931C1DB2F077537D8998@SHSMSX103.ccr.corp.intel.com>
Date: Mon, 23 Oct 2017 18:45:11 +0000
From: "Liang, Kan" <kan.liang@...el.com>
To: "acme@...nel.org" <acme@...nel.org>
CC: Ingo Molnar <mingo@...nel.org>,
"mingo@...hat.com" <mingo@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"peterz@...radead.org" <peterz@...radead.org>,
"jolsa@...nel.org" <jolsa@...nel.org>,
"wangnan0@...wei.com" <wangnan0@...wei.com>,
"hekuang@...wei.com" <hekuang@...wei.com>,
"namhyung@...nel.org" <namhyung@...nel.org>,
"alexander.shishkin@...ux.intel.com"
<alexander.shishkin@...ux.intel.com>,
"Hunter, Adrian" <adrian.hunter@...el.com>,
"ak@...ux.intel.com" <ak@...ux.intel.com>
Subject: RE: [PATCH V3 0/6] event synthesization multithreading for perf
record
> Em Mon, Oct 23, 2017 at 01:43:39PM +0000, Liang, Kan escreveu:
> > The plan is to do the multithreading step by step from the simplest case.
> > Synthesizing stage is just a start.
>
> > Only for synthesizing stage, I think the patch series should already
> > cover all the 'synthesizing' steps which can do multithreading. For
> > the rest 'synthesizing' steps, it only need to be done by single thread.
>
> > Since there is only multithreading for 'synthesizing' step, the
> > threads creation related code is event.c for now. It's better to move
> > it to a dedicate file and make it generic for recording threads. I think we can
> do it later separately.
>
> Yes, and I'm happy that you plan to continue working in this area, right? :-)
>
After reviewing my schedule, I'm afraid that I will not have the bandwidth
in this quarter to continue to support full multithreading.
I still have some other high priority items not finished yet.
I may revisit it after that. I'm sorry about that.
Thanks,
Kan
Powered by blists - more mailing lists