linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Dave Jones <davej@redhat.com>, Andrew Morton <akpm@osdl.org>,
	Ricky Beam <jfbeam@bluetronic.net>,
	nico-kernel@schottelius.org, linux-kernel@vger.kernel.org
Subject: Re: /proc/cpuinfo format - arch dependent!
Date: Sat, 7 May 2005 19:05:56 +0200	[thread overview]
Message-ID: <20050507170555.GA19329@alpha.home.local> (raw)
In-Reply-To: <20050507165357.GA19601@redhat.com>

Hi Dave,

On Sat, May 07, 2005 at 12:53:57PM -0400, Dave Jones wrote:
> On Sat, May 07, 2005 at 09:58:29AM +0200, Willy Tarreau wrote:
 
> What /could/ be useful would be a way to tell sched_setaffinity
> and co "I have two threads, I'd like them both to run on different cores,
> avoiding HT pairs, and never be migrated off them" without having to care
> about the layout of the cpus in each application.

Well, that's exactly for this that I formulated the proposal. A
CPU-intensive application which benefits from the cache would better
choose to run on HT pairs. A network-hungry application will prefer
running on only one sibling of each HT pair, and probably one process
per core, particularly when each core receives one NIC's interrupt.
A memory bandwidth intensive application will choose to run on a
single NUMA node, etc... So either the application can choose this
itself from its understanding of the CPU layout, or it can ask the
system "hey, I'd like this type of workload, how many process should
I start, and where should I bind them ?". I agree that the later
seems more portable and puts less burden on the application.

Regards,
Willy


  reply	other threads:[~2005-05-07 17:15 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19 12:15 /proc/cpuinfo format - arch dependent! Nico Schottelius
2005-04-19 13:24 ` Lennart Sorensen
2005-04-19 19:17   ` Lee Revell
2005-04-19 20:00     ` Nico Schottelius
2005-04-19 20:02       ` David S. Miller
2005-04-19 20:12       ` Lennart Sorensen
2005-04-19 20:42       ` Lee Revell
2005-04-19 20:54         ` Nico Schottelius
2005-04-19 21:12           ` Grzegorz Kulewski
2005-04-20 20:31   ` Ralf Baechle
2005-05-07  3:37 ` Ricky Beam
2005-05-07  4:01   ` Stefan Smietanowski
2005-05-07  7:55     ` Ricky Beam
2005-05-07 17:51       ` Stefan Smietanowski
2005-05-07 18:05         ` Ricky Beam
2005-05-07 18:46           ` Dr. David Alan Gilbert
2005-05-07  4:14   ` Andrew Morton
2005-05-07  7:58     ` Willy Tarreau
2005-05-07 16:53       ` Dave Jones
2005-05-07 17:05         ` Willy Tarreau [this message]
2005-05-07 17:20           ` Dave Jones
2005-05-07 17:18             ` Willy Tarreau
2005-05-08  1:25             ` Jim Nance
2005-05-08 16:11               ` John Kacur
2005-05-09 18:14               ` Bill Davidsen
2005-05-09 20:09                 ` Chris Friesen
2005-05-09 20:26                   ` Lennart Sorensen
2005-05-09 21:25                     ` Brian O'Mahoney
2005-05-10 16:21                   ` Bill Davidsen
2005-05-10 16:34                     ` Chris Friesen
2005-05-10  2:23                 ` Jim Nance
2005-05-10  4:12                   ` Willy Tarreau
2005-05-10  7:13                   ` Paul Jackson
2005-05-10 16:34                   ` Bill Davidsen
2005-05-07 17:54       ` Stefan Smietanowski
2005-05-07 18:05         ` Willy Tarreau
2005-05-09 18:03     ` Bill Davidsen
2005-05-10  7:21     ` Paul Jackson
2005-05-10 14:38       ` Lennart Sorensen
2005-05-10 16:37         ` Bill Davidsen
2005-05-09 18:00   ` Bill Davidsen
2005-05-09 19:58     ` Lennart Sorensen
2005-05-10 16:49       ` Bill Davidsen
     [not found] <3UZS7-5ue-17@gated-at.bofh.it>
     [not found] ` <41ouh-4QE-1@gated-at.bofh.it>
     [not found]   ` <41oXl-5hl-7@gated-at.bofh.it>
     [not found]     ` <41sxX-8cN-11@gated-at.bofh.it>
     [not found]       ` <41BL4-7l7-15@gated-at.bofh.it>
2005-05-07 23:33         ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>
2005-05-08 13:24           ` Andi Kleen

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=20050507170555.GA19329@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=jfbeam@bluetronic.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico-kernel@schottelius.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).