All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Cc: Andrew Morton <akpm@osdl.org>,
	torvalds@osdl.org, linux-kernel@vger.kernel.org,
	rohit.seth@intel.com
Subject: Re: [PATCH] Reading deterministic cache parameters and exporting it in /sysfs
Date: Fri, 18 Mar 2005 14:46:17 -0500	[thread overview]
Message-ID: <20050318194616.GH24385@redhat.com> (raw)
In-Reply-To: <20050318111847.A32361@unix-os.sc.intel.com>

On Fri, Mar 18, 2005 at 11:18:47AM -0800, Venkatesh Pallipadi wrote:
 > 
 > Here is the updated patch. 
 > 
 > I have seperated out the changes related to 
 > (1) using new method to determine cache size in existing /proc/cpuinfo and
 >     kernel boot messages (All but last hunk below)
 > (2) code to look at sharedness of the caches and store these details for future
 >     uses inside kernel and also exporting the cache details in /sysfs (last
 >     hunk in the patch)
 >   
 > Dave: Do you still feel having the cache details exported in /sysfs is a bad
 > idea? If yes, we can go ahead with the basic part of this patch (1 - above)
 > and look at (2) sometime later, as and when required.

tbh I think its just bloat, but if no-one else has any objections I won't oppose it.
The rest of the patch I have no problem with.

		Dave


      reply	other threads:[~2005-03-18 19:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-15 23:24 [PATCH] Reading deterministic cache parameters and exporting it in /sysfs Venkatesh Pallipadi
2005-03-15 23:36 ` Dave Jones
2005-03-16  0:10   ` Venkatesh Pallipadi
2005-03-16 10:29   ` Daniel Egger
2005-03-16  7:07 ` Andrew Morton
2005-03-18 19:18   ` Venkatesh Pallipadi
2005-03-18 19:46     ` Dave Jones [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=20050318194616.GH24385@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rohit.seth@intel.com \
    --cc=torvalds@osdl.org \
    --cc=venkatesh.pallipadi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.