From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Nominating Fengguang Wu - 0-day
Date: Fri, 29 Jul 2016 01:33:27 +0200 [thread overview]
Message-ID: <20160728233327.GC3296@wotan.suse.de> (raw)
In-Reply-To: <20160728230713.GB18980@wfg-t540p.sh.intel.com>
On Fri, Jul 29, 2016 at 07:07:13AM +0800, Fengguang Wu wrote:
> btw, maybe some maintainers are already informed: 0-day statistics
> show that ~60% errors can be reported in 2 hours, ~90% errors are
> reported in 24 hours and there are 1% errors reported after 1 week.
If one were to take 0-day code an slap it on some internal big-iron
server, and prioritize work for a few developers (say SUSE would do
this for its developers) do you expect the turnaround time for
reports would be faster if we had bigger-meaner hardware ? These
days actually would like to get results back in a few minutes
for 90% of errors so wondering how / if others have taken on
0-day internally and made it faster by beefing up the hardware.
Luis
next prev parent reply other threads:[~2016-07-28 23:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 19:01 [Ksummit-discuss] Nominating Fengguang Wu - 0-day Luis R. Rodriguez
2016-07-25 20:23 ` Alexandre Belloni
2016-07-26 3:10 ` Vinod Koul
2016-07-26 8:16 ` Laurent Pinchart
2016-07-26 8:56 ` Vinod Koul
2016-07-28 13:20 ` Fengguang Wu
2016-07-27 14:50 ` Fengguang Wu
2016-07-28 16:15 ` Laurent Pinchart
2016-07-28 20:53 ` Fengguang Wu
2016-07-28 20:59 ` Laurent Pinchart
2016-07-28 22:38 ` Dmitry Torokhov
2016-07-29 16:26 ` Vinod Koul
2016-07-28 23:07 ` Fengguang Wu
2016-07-28 23:33 ` Luis R. Rodriguez [this message]
2016-07-29 0:09 ` Fengguang Wu
2016-07-29 15:12 ` Bjorn Helgaas
2016-07-30 17:05 ` Luis R. Rodriguez
2016-07-30 17:24 ` Guenter Roeck
2016-07-31 6:35 ` Fengguang Wu
2016-07-31 17:32 ` Vinod Koul
2016-08-01 13:35 ` Fengguang Wu
2016-07-28 23:38 ` Jiri Kosina
2016-07-31 11:16 ` Fengguang Wu
2016-07-29 2:00 ` Steven Rostedt
2016-07-29 2:26 ` Fengguang Wu
2016-07-27 14:41 ` Fengguang Wu
2016-07-28 17:15 ` Guenter Roeck
2016-07-28 17:21 ` Dmitry Vyukov
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=20160728233327.GC3296@wotan.suse.de \
--to=mcgrof@kernel.org \
--cc=fengguang.wu@intel.com \
--cc=ksummit-discuss@lists.linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.