public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: Borislav Petkov <bp@amd64.org>
Cc: tony.luck@intel.com, andi@firstfloor.org, ananth@in.ibm.com,
	x86@kernel.org, linux-kernel@vger.kernel.org, mingo@redhat.com,
	hpa@zytor.com, tglx@linutronix.de, linux-edac@vger.kernel.org
Subject: Re: [PATCH RFC] x86/mce: Move MCE sysfs attributes out of the per-cpu location
Date: Wed, 29 Aug 2012 18:40:52 +0530	[thread overview]
Message-ID: <503E14DC.3060507@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120829104018.GD26977@aftab.osrc.amd.com>

On 08/29/2012 04:10 PM, Borislav Petkov wrote:
> On Wed, Aug 29, 2012 at 03:56:04PM +0530, Naveen N. Rao wrote:
>> Hmmm.. Can't we just deprecate these? ;) Perhaps we can consider
>> adding newer tunables in the right place.
>
> In case you haven't noticed yet: I'm all on your side.

Yup, I know :)

I had my doubts when I sent this patch (hence the RFC tag) and I was 
only wondering above if it'll be a good idea to limit such tunables 
going forward. We could force all _new_ MCE tunables to be global, 
except where they actually apply on a per-processor basis.

>
> But let me ask you this: these attributes grow to a large number with
> a large number of cores but why is this a problem? We have a bunch of
> redundant attributes in sysfs, so what?
>
> See what I mean?
>

Well, it's ugly and does not make much sense, as I'm sure you noticed. 
On a 10-core, 8-socket machine with HT, we'll end up with nearly a 
thousand such entries!

I don't know how much resource this takes up (if any) and like you said, 
this may just be a "so what?", but I wanted to bring this up and see if 
we could/want to do anything about this. I'm certainly fine if we want 
to ignore this.


Thanks,
Naveen


  reply	other threads:[~2012-08-29 13:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29  7:41 [PATCH RFC] x86/mce: Move MCE sysfs attributes out of the per-cpu location Naveen N. Rao
2012-08-29 10:13 ` Borislav Petkov
2012-08-29 10:26   ` Naveen N. Rao
2012-08-29 10:40     ` Borislav Petkov
2012-08-29 13:10       ` Naveen N. Rao [this message]
2012-08-29 14:43   ` Luck, Tony
2012-08-30  9:47     ` Naveen N. Rao

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=503E14DC.3060507@linux.vnet.ibm.com \
    --to=naveen.n.rao@linux.vnet.ibm.com \
    --cc=ananth@in.ibm.com \
    --cc=andi@firstfloor.org \
    --cc=bp@amd64.org \
    --cc=hpa@zytor.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=x86@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