From: Borislav Petkov <bp@alien8.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Russ Anderson <rja@hpe.com>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
Justin Ernst <justin.ernst@hpe.com>,
russ.anderson@hpe.com, Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
Aristeu Rozanski Filho <arozansk@redhat.com>
Subject: Re: [PATCH] Raise maximum number of memory controllers
Date: Thu, 27 Sep 2018 06:52:44 +0200 [thread overview]
Message-ID: <20180927045244.GA30912@zn.tnic> (raw)
In-Reply-To: <20180926230257.GA5666@agluck-desk>
On Wed, Sep 26, 2018 at 04:02:57PM -0700, Luck, Tony wrote:
> We don't have stats, nor control of power on a per memory controller
> or per dimm basis. So all these files are just noise.
Yeah, and also, looking at your previous mail, stuff like:
/sys/bus/mc6/devices/dimm0
/sys/bus/mc4/devices/dimm0
doesn't make any sense: why is mc* directly under bus? It should be
under ...bus/edac/mc/...
We'll have to clean it up carefully, when there's time.
> But ... we are at -rc5. Not sure that we'll figure out, write, test & debug
> the proper solution in the next 3-4 weeks. So perhaps we should apply
>
> -#define EDAC_MAX_MCS 16
> +#define EDAC_MAX_MCS 64
>
> as a temporary band-aid to get HPE's 32-socket machine running while
> we work on the proper fix?
Yeah, after sleeping on it I see it the same way - band-aid it now and
clean it up properly later.
Thx.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2018-09-27 4:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 14:34 [PATCH] Raise maximum number of memory controllers Justin Ernst
2018-09-25 15:26 ` Borislav Petkov
2018-09-25 17:50 ` Luck, Tony
2018-09-25 18:07 ` Borislav Petkov
2018-09-26 9:35 ` Borislav Petkov
2018-09-26 15:27 ` Borislav Petkov
2018-09-26 16:03 ` Mauro Carvalho Chehab
2018-09-26 16:17 ` Borislav Petkov
2018-09-26 17:39 ` Mauro Carvalho Chehab
2018-09-26 18:10 ` Luck, Tony
2018-09-26 18:23 ` Russ Anderson
2018-09-26 23:02 ` Luck, Tony
2018-09-27 4:52 ` Borislav Petkov [this message]
2018-09-27 21:44 ` Luck, Tony
2018-09-27 22:03 ` Borislav Petkov
2018-09-28 1:10 ` Mauro Carvalho Chehab
2018-10-01 12:47 ` Borislav Petkov
2018-10-01 22:43 ` [PATCH] EDAC: Don't add devices under /sys/bus/edac Luck, Tony
2018-10-02 1:22 ` Mauro Carvalho Chehab
2018-10-02 15:51 ` Ernst, Justin
2018-10-02 16:26 ` Borislav Petkov
2018-11-06 14:45 ` Borislav Petkov
2018-11-13 19:09 ` Ernst, Justin
2018-11-13 19:15 ` Borislav Petkov
2018-09-26 7:55 ` [PATCH] Raise maximum number of memory controllers Zhuo, Qiuxu
2018-09-26 13:53 ` Russ Anderson
2018-09-26 16:13 ` Aristeu Rozanski
2018-09-27 5:56 ` Borislav Petkov
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=20180927045244.GA30912@zn.tnic \
--to=bp@alien8.de \
--cc=arozansk@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=justin.ernst@hpe.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=mchehab@kernel.org \
--cc=rja@hpe.com \
--cc=russ.anderson@hpe.com \
--cc=tony.luck@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;
as well as URLs for NNTP newsgroup(s).