linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-mm@kvack.org, nitin.a.kamble@intel.com,
	jun.nakajima@intel.com, asit.k.mallick@intel.com,
	sunil.saxena@intel.com
Subject: Re: 2.5.59-mm2
Date: 18 Jan 2003 21:12:41 +0100	[thread overview]
Message-ID: <1042920761.15782.5.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20030118002027.2be733c7.akpm@digeo.com>

[-- Attachment #1: Type: text/plain, Size: 586 bytes --]


> +kirq-up-fix.patch
> 
>  Fix the kirq build for non-SMP

Hi,

Is there any reason to put this complexity in the kernel instead of
doing it from a userspace daemon?

A userspace daemon can do higher level evaluations, read config files
about the system (like numa configuration etc etc) and all 2.4/2.5
kernels already have a userspace api for setting irq affinity..

an example of a simple version of such daemon is:
http://people.redhat.com/arjanv/irqbalance/irqbalance-0.03.tar.gz

any chance of testing this in an intel lab?

Greetings,
     Arjan van de Ven

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-01-18 20:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-18  8:20 2.5.59-mm2 Andrew Morton
2003-01-18 20:12 ` Arjan van de Ven [this message]
2003-01-19  7:46 ` 2.5.59mm2 BUG at fs/jbd/transaction.c:1148 Mike Galbraith
2003-01-19  8:05   ` Andrew Morton
2003-01-19  8:04     ` Mike Galbraith
2003-01-19  8:57       ` Andrew Morton
2003-01-19  8:06     ` Mike Galbraith
2003-01-19 19:45 2.5.59-mm2 Nakajima, Jun
2003-01-19 20:18 ` 2.5.59-mm2 Arjan van de Ven
2003-01-19 21:44 2.5.59-mm2 Nakajima, Jun
2003-01-19 22:05 ` 2.5.59-mm2 Andrew Morton

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=1042920761.15782.5.camel@laptop.fenrus.com \
    --to=arjanv@redhat.com \
    --cc=akpm@digeo.com \
    --cc=asit.k.mallick@intel.com \
    --cc=jun.nakajima@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=nitin.a.kamble@intel.com \
    --cc=sunil.saxena@intel.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