mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: [patch] Add allowed_affinity to the irq_desc to make it possible to have restricted irqs
Date: Thu, 14 Dec 2006 01:22:08 -0700	[thread overview]
Message-ID: <m1psamopjj.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <45810383.2060708@linux.intel.com> (Arjan van de Ven's message of "Thu, 14 Dec 2006 08:55:47 +0100")

Arjan van de Ven <arjan@linux.intel.com> writes:

> Eric W. Biederman wrote:
>> What is the problem you are trying to solve?
>
> 2 problems
> 1) irq's that irqbalance should not touch at all

This is easy we just need a single bit.  Not 128+ bytes on the huge
machines.

> 2) irqs that can only go to a subset of processors.
>
> 1) is very real today
> 2) is partially real on some of the bigger numa stuff already.

You have said you the NUMA cases is handled in another way already?
In which case irqs that can only got to a subset of processors
shouldn't be a problem.

Eric

  reply	other threads:[~2006-12-14  8:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-13 13:53 Arjan van de Ven
2006-12-13 19:41 ` Eric W. Biederman
2006-12-13 19:43   ` Ingo Molnar
2006-12-13 20:06     ` Eric W. Biederman
2006-12-13 20:19       ` Ingo Molnar
2006-12-13 20:23       ` Arjan van de Ven
2006-12-14  4:14         ` Eric W. Biederman
2006-12-14  6:24           ` Yinghai Lu
2006-12-14  7:55           ` Arjan van de Ven
2006-12-14  8:22             ` Eric W. Biederman [this message]
2006-12-14  8:23               ` Arjan van de Ven
2006-12-14  8:34                 ` Eric W. Biederman
2006-12-14  8:40                   ` Arjan van de Ven
2006-12-13 20:02   ` Arjan van de Ven
2006-12-13 20:16     ` Eric W. Biederman

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=m1psamopjj.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=arjan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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
all inboxes | Powered by JetHome®