[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160323100220.GX6344@twins.programming.kicks-ass.net>
Date: Wed, 23 Mar 2016 11:02:20 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Wang Nan <wangnan0@...wei.com>
Cc: mingo@...hat.com, linux-kernel@...r.kernel.org,
He Kuang <hekuang@...wei.com>,
Alexei Starovoitov <ast@...nel.org>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Brendan Gregg <brendan.d.gregg@...il.com>,
Jiri Olsa <jolsa@...nel.org>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
Namhyung Kim <namhyung@...nel.org>,
Zefan Li <lizefan@...wei.com>, pi3orama@....com
Subject: Re: [PATCH 5/5] perf core: Reduce perf event output overhead by new
overflow handler
On Mon, Mar 14, 2016 at 09:59:45AM +0000, Wang Nan wrote:
> By creating onward and backward specific overflow handlers and setting
> them according to event's backward setting, normal sampling events
> don't need checking backward setting of an event any more.
The normal antonym of backward is forward. Onward does not indicate a
direction per se, its more a continuance or progression of a previously
set goal.
Also, just squash these last two patches together.
Powered by blists - more mailing lists