[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 5 May 2021 23:13:30 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Tyler Hicks <tyhicks@...ux.microsoft.com>,
Borislav Petkov <bp@...en8.de>
CC: wangglei <wangglei@...il.com>,
"Lei Wang (DPLAT)" <Wang.Lei@...rosoft.com>,
"mchehab@...nel.org" <mchehab@...nel.org>,
"james.morse@....com" <james.morse@....com>,
"rric@...nel.org" <rric@...nel.org>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Hang Li <hangl@...rosoft.com>,
Brandon Waller <bwaller@...rosoft.com>
Subject: RE: [EXTERNAL] Re: [PATCH] EDAC: update edac printk wrappers to use
printk_ratelimited.
>> What is your situation? ARM?
>
> Yes, though I'm not sure if those additional features are
> important/useful enough for us to generalize that driver. The main
> motivation here was just to prevent storage/network from being flooded
> by obviously-bad nodes that haven't been offlined yet. :)
>
> Lei and others on cc will need to evaluate porting cec.c and what it
> will gain them. Thanks again.
Tyler,
You might also look at the x86 "storm" detection code (tl;dr version
"If error interrupts are coming too fast, turn off the interrupts and poll").
-Tony
Powered by blists - more mailing lists