From: Doug Thompson <norsk5@yahoo.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] EDAC and the sysfs
Date: Mon, 14 Nov 2005 17:12:57 -0800 (PST) [thread overview]
Message-ID: <20051115011257.825.qmail@web50115.mail.yahoo.com> (raw)
In-Reply-To: <20051115004704.91557.qmail@web50106.mail.yahoo.com>
--- Doug Thompson <norsk5@yahoo.com> wrote:
> What is EDAC and what does it stand for?
>
> EDAC= Error Detection And Correction.
> > For PCI Parity Error detection controls and
> > information files:
> >
> > /sys/devices/system/edac/pci
>
> That kind of controls and files?
I left out new PCI whitelist/blacklist control files I
am also working on:
pci_parity_whitelist
pci_parity_blacklist
Since some unmentioned (and expensive) pci boards fail
to conform with the PCI spec when dealing with PCI
parity status reporting (or they just plain have
bugs), the pci scanning feature needs a whitelist or
a blacklist of "vendor_id:device_id" to specificly
scan or not scan.
If there is a whitelist, no blacklist occurs. When a
blacklist is written to, the whitelist is erased and
devices on blacklist are skipped on the scanning.
format of info to write to these controls, in hex:
vendor_id:device_id[,vendor_id:device_id...]
I have timed both ECC scanning and PCI parity
scanning.
ECC scanning on a dual opteron is 170 TSC clocks.
PCI Parity for 24 devices is 65000 TSC clocks. Ouch!
When all devices are blacklisted, the iterator is 2700
TSC clocks.
doug t
"If you think Education is expensive, just try Ignorance"
"Don't tell people HOW to do things, tell them WHAT you
want and they will surprise you with their ingenuity."
Gen George Patton
next prev parent reply other threads:[~2005-11-15 1:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 22:14 Doug Thompson
2005-11-14 22:31 ` Greg KH
2005-11-15 0:30 ` Dave Jones
2005-11-15 17:24 ` Greg KH
2005-11-15 0:47 ` Doug Thompson
2005-11-15 1:12 ` Doug Thompson [this message]
2005-11-15 17:25 ` Greg KH
2005-11-16 0:26 ` Doug Thompson
2005-11-17 7:05 ` Greg KH
2005-11-17 17:20 ` Doug Thompson
2005-11-17 17:18 ` Greg KH
2005-11-17 18:32 ` Kay Sievers
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=20051115011257.825.qmail@web50115.mail.yahoo.com \
--to=norsk5@yahoo.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®