Mailing List ArchivesAuthenticated access |
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}
|
Mailing List ArchivesAuthenticated access |
|
| Date: | Thu, 26 Jun 2008 14:10:02 -0700 |
|---|---|
| From: | Cen Kwang Ge <cge@xxxxxxxx> |
| Subject: | [Gems-users] conflict resolution in LogTM |
Hi,from the gen-scripts.py, when using Hybrid and Timestamp conflict resolution policies in EE (eager version management and eager conflict detection), XACT_NO_BACKOFF is set to 1 meaning that exponential backoff after abort is disabled. Is there a reason for this?I tried to use Hybrid and Timestamp policies with XACT_NO_BACKOFF = 0 with 16 processors, but get segmentation fault. Any idea why this happened? Thanks, Cen |
| Previous by Date: | [Gems-users] L2 cache miss actions, Konstantinos Nikas |
|---|---|
| Next by Date: | [Gems-users] A problem about install simicsfs, llccdd1985 |
| Previous by Thread: | Re: [Gems-users] LogTM Transactions Hanging (Gems 2.1), Fuad Tabba |
| Next by Thread: | Re: [Gems-users] conflict resolution in LogTM, Luke Yen |
| Indexes: | [Date] [Thread] |