public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Anatol Pomozov <anatol.pomozov@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Solving M produces N consumers scalability problem
Date: Mon, 4 Nov 2013 21:28:06 +0100	[thread overview]
Message-ID: <20131104202806.GL29695@two.firstfloor.org> (raw)
In-Reply-To: <CAOMFOmVrBB5Pj9hXaooQF1XNkLqUW-LBux5jbsrYArnpQh5iCg@mail.gmail.com>

> This solution pretty-much equivalent to per-CPU data structures. And

No it's not, it doesn't require one queue per CPU.

A CPU these days isn't really a CPU anymore, but often a CPU thread,
which is much more light weight. So having a queue per CPU is often
total overkill, and amplifies any per queue costs (like invalidation)

-Andi

      reply	other threads:[~2013-11-04 20:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 20:48 Solving M produces N consumers scalability problem Anatol Pomozov
2013-11-04 18:53 ` Andi Kleen
2013-11-04 20:23   ` Anatol Pomozov
2013-11-04 20:28     ` Andi Kleen [this message]

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=20131104202806.GL29695@two.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=anatol.pomozov@gmail.com \
    --cc=linux-kernel@vger.kernel.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