DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Christensen <drc@linux.vnet.ibm.com>
To: Tom Barbette <barbette@kth.se>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Performance impact of "declaring" more CPU cores
Date: Fri, 25 Oct 2019 10:35:50 -0700	[thread overview]
Message-ID: <f061d171-b9d5-eabd-6868-0169a5f7eace@linux.vnet.ibm.com> (raw)
In-Reply-To: <f46a3505-a4cd-d4a3-7429-ea5b29ca4b28@kth.se>

> The only useful observation we made is that when we are in a "bad case", 
> the LLC has more cache misses.

Have you looked closely at the CPU topology on your platform, can you 
provide some examples here of what you're seeing?  The hwloc package is 
very useful in visualizing how your logical cores map to CPU cache. 
There may be benefit is more strategically selecting the lcores you use 
to reduce LLC cache mssies.

Dave

  reply	other threads:[~2019-10-25 17:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 17:32 Tom Barbette
2019-10-25 17:35 ` David Christensen [this message]
2019-10-30 17:20   ` Tom Barbette

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=f061d171-b9d5-eabd-6868-0169a5f7eace@linux.vnet.ibm.com \
    --to=drc@linux.vnet.ibm.com \
    --cc=barbette@kth.se \
    --cc=dev@dpdk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).