From: Tim Chen <tim.c.chen@linux.intel.com>
To: Feng Tang <feng.tang@intel.com>, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Shakeel Butt <shakeelb@google.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Joe Mario <jmario@redhat.com>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Eric Dumazet <edumazet@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
dave.hansen@intel.com, ying.huang@intel.com,
tim.c.chen@intel.com, andi.kleen@intel.com
Subject: Re: [PATCH v3] Documentation: Add document for false sharing
Date: Wed, 05 Apr 2023 16:29:08 -0700 [thread overview]
Message-ID: <f33ce1e75b5fec0a36c6670e1301fed4450d86ae.camel@linux.intel.com> (raw)
In-Reply-To: <2520c3d060e7b77560ea32a4b132d8e1a5f14ac9.camel@linux.intel.com>
On Wed, 2023-04-05 at 15:38 -0700, Tim Chen wrote:
> Thanks for the update. Looks good. Some minor nits to improve readability.
>
> On Tue, 2023-04-04 at 13:22 +0800, Feng Tang wrote:
> >
> > +
> > +False sharing could easily happen unless they are intentionally
> > +checked, and it is valuable to run specific tools for performance
> > +critical workloads to detect false sharing affecting performance case
> > +and optimize accordingly.
> > +
> > +
> > +How to detect and analysis False Sharing
>
> s/analysis/analyse
s/analysis/analyze
Fix my typo.
Tim
next prev parent reply other threads:[~2023-04-05 23:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 5:22 [PATCH v3] Documentation: Add document for false sharing Feng Tang
2023-04-04 19:38 ` Shakeel Butt
2023-04-05 22:38 ` Tim Chen
2023-04-05 23:29 ` Tim Chen [this message]
2023-04-06 1:14 ` Feng Tang
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=f33ce1e75b5fec0a36c6670e1301fed4450d86ae.camel@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andi.kleen@intel.com \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@intel.com \
--cc=edumazet@google.com \
--cc=feng.tang@intel.com \
--cc=jmario@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=shakeelb@google.com \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=ying.huang@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