From: "Liang, Kan" <kan.liang@linux.intel.com>
To: David Miller <davem@davemloft.net>
Cc: acme@kernel.org, linux-kernel@vger.kernel.org,
wangnan0@huawei.com, jolsa@kernel.org, namhyung@kernel.org,
kan.liang@intel.com, ak@linux.intel.com, yao.jin@linux.intel.com,
peterz@infradead.org
Subject: Re: [PATCHES/RFC] Re: A concern about overflow ring buffer mode
Date: Mon, 29 Oct 2018 13:42:56 -0400 [thread overview]
Message-ID: <b488a063-276c-ab8f-954e-f68e951146b4@linux.intel.com> (raw)
In-Reply-To: <20181029.104008.791032322062574758.davem@davemloft.net>
On 10/29/2018 1:40 PM, David Miller wrote:
> From: "Liang, Kan" <kan.liang@linux.intel.com>
> Date: Mon, 29 Oct 2018 10:33:06 -0400
>
>> I just realized that the problem in KNL will be back if we switch
>> back to non-overwrite mode.
>
> What is KNL?
>
Intel Xeon Phi Processor, Knights Landing.
Thanks,
Kan
next prev parent reply other threads:[~2018-10-29 17:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 17:45 David Miller
2018-10-26 18:38 ` Arnaldo Carvalho de Melo
2018-10-26 18:42 ` Arnaldo Carvalho de Melo
2018-10-26 19:02 ` Arnaldo Carvalho de Melo
2018-10-26 19:07 ` Liang, Kan
2018-10-26 19:12 ` Arnaldo Carvalho de Melo
2018-10-26 19:16 ` Liang, Kan
2018-10-26 19:24 ` Arnaldo Carvalho de Melo
2018-10-26 20:11 ` Liang, Kan
2018-10-26 20:43 ` Arnaldo Carvalho de Melo
2018-10-29 13:03 ` [PATCHES/RFC] " Arnaldo Carvalho de Melo
2018-10-29 14:33 ` Liang, Kan
2018-10-29 14:35 ` Arnaldo Carvalho de Melo
2018-10-29 15:11 ` Liang, Kan
2018-10-29 17:43 ` David Miller
2018-10-29 17:56 ` Arnaldo Carvalho de Melo
2018-10-29 17:40 ` David Miller
2018-10-29 17:42 ` Liang, Kan [this message]
2018-10-29 17:48 ` David Miller
2018-10-29 18:20 ` Liang, Kan
2018-10-29 18:32 ` Arnaldo Carvalho de Melo
2018-10-29 22:32 ` Liang, Kan
2018-10-29 22:42 ` David Miller
2018-10-30 1:54 ` Liang, Kan
2018-10-29 21:16 ` David Miller
2018-10-29 17:55 ` Arnaldo Carvalho de Melo
2018-10-30 19:05 ` David Miller
2018-10-31 22:03 ` [tip:perf/urgent] perf top: Do not use overwrite mode by default tip-bot for Arnaldo Carvalho de Melo
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=b488a063-276c-ab8f-954e-f68e951146b4@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=davem@davemloft.net \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=wangnan0@huawei.com \
--cc=yao.jin@linux.intel.com \
/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
all inboxes | Powered by JetHome®