Date: Tue, 10 May 2005 06:12:37 +0200
From: Willy Tarreau <willy@w.ods.org>
To: Jim Nance <jlnance@sdf.lonestar.org>
Cc: Bill Davidsen <davidsen@tmr.com>, 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!
Message-ID: <20050510041237.GA32065@alpha.home.local>
References: <20050508012521.GA24268@SDF.LONESTAR.ORG> <427FA876.7000401@tmr.com> <20050510022301.GA13763@SDF.LONESTAR.ORG>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050510022301.GA13763@SDF.LONESTAR.ORG>
User-Agent: Mutt/1.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1275
Lines: 28

Hi Jim,

On Tue, May 10, 2005 at 02:23:01AM +0000, Jim Nance wrote:
 
> Now I know there are exceptions to rules.  But in general I would say
> that if an application needs to know about the configuration of the
> processors, then its compensating for shortcommings in the kernel.

I cannot agree. When an application needs to know such things, it is
because it has being developped primarily for a certain platform and
optimized for such platform. The kernel's scheduler is written for a
general purpose and not for some particular apps which will run two
concurrent threads at 100% CPU each for example, with lots of memory
exchanges through the CPU cache. It is not uncommon to have to manually
play with /proc before starting some specific apps. It is for this case
that some help from the kernel might be welcome. Instead of forcing eth0
interrupt to CPU0 then binding your process to CPU0, you might prefer to
tell the kernel "this app needs to run on the CPU which receives ints
from eth0", whatever it is.

Regards,
willy

-
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/