public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Burkhardt <marc@osknowledge.org>
To: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
Cc: Marc Burkhardt <marc@osknowledge.org>, linux-kernel@vger.kernel.org
Subject: Re: Slowdown due to threads bouncing between HT cores
Date: Sat, 4 Oct 2014 11:22:05 +0200	[thread overview]
Message-ID: <20141004092205.GA12973@localhost> (raw)
In-Reply-To: <20141003211417.GA17326@sesse.net>

* Steinar H. Gunderson <sgunderson@bigfoot.com> [2014-10-03 23:14:17 +0200]:

> On Fri, Oct 03, 2014 at 11:11:52PM +0200, Marc Burkhardt wrote:
> > As I understand your mail, you problem is quite similar, isn't it?
> 
> I guess it depends on how often your process migrates. If it happens, like,
> every second, it's not a big problem (and probably is expected).
> If it happens all the time, it might be; it depends a bit on a number of
> factors.

Hi Steinar,

you say the behavior is probably expected, but I still don't get the point why
this could be normal or even wanted. There's a cost for migrating the process to
another CPU. In case my machine has 4 cores, 3 of them 'idle' and that 1 running
process that keeps being migrated ... where's the benefit of migrating it?

Do you have any source/docs where I could read about this?

Thanks,
Marc

> 
> /* Steinar */
> -- 
> Homepage: http://www.sesse.net/
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

-- 
Marc Burkhardt

  reply	other threads:[~2014-10-04  9:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-03 19:44 Slowdown due to threads bouncing between HT cores Steinar H. Gunderson
2014-10-03 21:11 ` Marc Burkhardt
2014-10-03 21:14   ` Steinar H. Gunderson
2014-10-04  9:22     ` Marc Burkhardt [this message]
2014-10-04 13:41 ` Andi Kleen
2014-10-04 14:12   ` Steinar H. Gunderson
2014-10-04 14:50 ` Chuck Ebbert
2014-10-05 11:19   ` Steinar H. Gunderson
2014-10-08 15:37 ` bisected: futex regression >= 3.14 - was - " Mike Galbraith
2014-10-08 16:14   ` Thomas Gleixner
2014-10-08 16:45     ` Steinar H. Gunderson
2014-10-08 17:52       ` Mike Galbraith
2014-10-08 16:23   ` Steinar H. Gunderson
2014-10-08 17:04   ` Linus Torvalds
2014-10-08 17:05     ` Steinar H. Gunderson
2014-10-08 17:59     ` Mike Galbraith
2014-10-24 15:25       ` Thomas Gleixner
2014-10-24 16:38         ` Mike Galbraith
2014-10-26 10:39           ` Steinar H. Gunderson
2014-10-26 13:16             ` Mike Galbraith
2014-10-26 13:58               ` Mike Galbraith
2014-10-26 14:11                 ` Steinar H. Gunderson
2014-10-26 14:41                   ` Mike Galbraith
2014-10-27 10:05                   ` Mike Galbraith

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=20141004092205.GA12973@localhost \
    --to=marc@osknowledge.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sgunderson@bigfoot.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