Jump to content

MESIF protocol: Revision history


For any version listed below, click on its date to view it. For more help, see Help:Page history and Help:Edit summary. (cur) = difference from current version, (prev) = difference from preceding version, m = minor edit, → = section edit, ← = automatic edit summary

26 February 2025

3 September 2024

9 June 2024

8 June 2024

15 March 2024

  • curprev 11:1611:16, 15 March 2024 97.102.205.224 talk 6,297 bytes +172 Correct erroneous statement that reads from main memory start in the S state. They start in the F state. The only way to enter the S state is to hand the F state over to another cache. undo

27 March 2023

30 September 2019

10 January 2018

6 September 2017

27 April 2017

1 February 2017

26 October 2016

15 October 2016

10 September 2016

18 July 2016

20 June 2016

19 June 2016

21 March 2014

11 March 2013

12 September 2012

22 August 2012

13 May 2012

26 January 2012

  • curprev 02:4002:40, 26 January 2012 130.216.30.113 talk 2,146 bytes +1 The protocol does not require any cached line to have one node in F state. If a node in F state wishes to delete its copy, it can simply purge it, leaving no F state cache line, but possibly others in S state. Table 3 confirms this. --jrg undo

27 September 2011

7 June 2011

29 January 2011

3 February 2010

8 October 2009

6 October 2009