From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1031498Ab2COBiB (ORCPT ); Wed, 14 Mar 2012 21:38:01 -0400 Received: from mx1.redhat.com ([209.132.183.28]:41614 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031187Ab2COBh7 (ORCPT ); Wed, 14 Mar 2012 21:37:59 -0400 Message-ID: <4F6147E8.3020409@redhat.com> Date: Wed, 14 Mar 2012 22:37:44 -0300 From: Mauro Carvalho Chehab User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1 MIME-Version: 1.0 To: Greg KH CC: Borislav Petkov , Linux Edac Mailing List , Linux Kernel Mailing List Subject: Re: [PATCH 0/6] Add a per-dimm structure References: <1331120438-27523-1-git-send-email-mchehab@redhat.com> <20120313233217.GB31106@kroah.com> <4F60F2E4.7060707@redhat.com> <20120314204355.GA10187@kroah.com> <20120314223102.GA27602@aftab> <20120314224050.GA32297@kroah.com> In-Reply-To: <20120314224050.GA32297@kroah.com> X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em 14-03-2012 19:40, Greg KH escreveu: > On Wed, Mar 14, 2012 at 11:31:02PM +0100, Borislav Petkov wrote: >> On Wed, Mar 14, 2012 at 01:43:55PM -0700, Greg KH wrote: >>>> He thinks that a multi-layer struct should be created inside that directory >>>> (it could have 2 or 3 levels of directories, depending on how the memory is >>>> organized at the memory controller), instead of having a large number of files >>>> there. >>> >>> Why create subdirs? If those subdirectories are not real devices, >>> showing a real hierarchy, then do not create them as userspace will get >>> very confused very quickly. >> >> Why, IMO, we agreed on the following layout >> >> rank0/ >> |-- dimm_dev_type >> |-- dimm_edac_mode >> |-- dimm_label >> |-- dimm_location >> |-- dimm_mem_type >> |-- CE >> |-- UE >> `-- dimm_size >> >> with CE being the correctable errors counter and UE be optional and only >> present when it makes sense for the hardware. >> >> This is not multi-layered, it is very easy to implement and mirrors all >> possible memory controllers from the point of view of the single DIMM. >> no? Or am I missing something...? > > Looks fine to me, assuming "rankX" is the dimm itself? The node name can be either "rankX" or "dimmX", depending if the memory controller is able to detect wich memory ranks belong to each DIMM or not. > > greg k-h > -- > To unsubscribe from this list: send the line "unsubscribe linux-edac" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html