I think Brad's on vacation right now. When he gets back I'm sure he'll
take care of this.
Gabe
Quoting Konstantinos Aisopos <[email protected]>:
That's great. Yes, please use "Konstantinos Aisopos"
-Kostas
On Thu, Sep 15, 2011 at 2:54 PM, Gabriel Michael Black
<[email protected]> wrote:
You do, but someone can take care of it for you. Maybe Brad? You're name
will be on the commit but one of us will actual push it up. Let us know if
you want your name to be something other than what you've been using for
email/reviews.
Gabe
Quoting Konstantinos Aisopos <[email protected]>:
hi,
I got the green signal to submit my patch (GARNET: adding a fault model
for
resilient on-chip network research) and I was wondering if I need any
permissions to push it to the main repo.
thanks,
-Kostas
---------- Forwarded message ----------
From: Brad Beckmann <[email protected]>
Date: Wed, Sep 14, 2011 at 8:42 PM
Subject: Re: Review Request: GARNET: adding a fault model for resilient
on-chip network research.
To: Ali Saidi <[email protected]>, Gabe Black <[email protected]>,
Nathan
Binkert <[email protected]>, Steve Reinhardt <[email protected]>, Brad
Beckmann <[email protected]>, Tushar Krishna <[email protected]>
Cc: Konstantinos Aisopos <[email protected]>, Default <
[email protected]>
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/776/
Ship it!
Thanks for you hard work. This looks good to me.
- Brad
On August 18th, 2011, 2:58 p.m., Konstantinos Aisopos wrote:
Review request for Default, Ali Saidi, Gabe Black, Steve Reinhardt,
Nathan
Binkert, Brad Beckmann, and Tushar Krishna.
By Konstantinos Aisopos.
*Updated 2011-08-18 14:58:55*
Description
GARNET: adding a fault model for resilient on-chip network research.
This patch adds a fault model, which provides the probability of a number
of
architectural faults in the interconnection network (e.g., data
corruption,
misrouting). These probabilities can be used to realistically inject
faults
in GARNET and faithfully evaluate the effectiveness of novel resilient NoC
architectures.
Diffs
- configs/ruby/Ruby.py (889818c58eff)
- src/mem/ruby/network/fault_model/FaultModel.hh (PRE-CREATION)
- src/mem/ruby/network/fault_model/FaultModel.cc (PRE-CREATION)
- src/mem/ruby/network/fault_model/FaultModel.py (PRE-CREATION)
- src/mem/ruby/network/fault_model/SConscript (PRE-CREATION)
- src/mem/ruby/network/garnet/BaseGarnetNetwork.hh (889818c58eff)
- src/mem/ruby/network/garnet/BaseGarnetNetwork.cc (889818c58eff)
- src/mem/ruby/network/garnet/BaseGarnetNetwork.py (889818c58eff)
- src/mem/ruby/network/garnet/fixed-pipeline/GarnetNetwork_d.hh
(889818c58eff)
- src/mem/ruby/network/garnet/fixed-pipeline/GarnetNetwork_d.cc
(889818c58eff)
- src/mem/ruby/network/garnet/fixed-pipeline/Router_d.hh (889818c58eff)
- src/mem/ruby/network/garnet/fixed-pipeline/Router_d.cc (889818c58eff)
View Diff <http://reviews.m5sim.org/r/776/diff/>
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
