Update of /cvsroot/monetdb/MonetDB/src/gdk
In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv24839

Modified Files:
      Tag: MonetDB_1-22
        gdk_bat.mx gdk_bbp.mx gdk_heap.mx 
Log Message:
more \_ -> _ changes


Index: gdk_bbp.mx
===================================================================
RCS file: /cvsroot/monetdb/MonetDB/src/gdk/gdk_bbp.mx,v
retrieving revision 1.208.2.3
retrieving revision 1.208.2.4
diff -u -d -r1.208.2.3 -r1.208.2.4
--- gdk_bbp.mx  5 Feb 2008 22:00:32 -0000       1.208.2.3
+++ gdk_bbp.mx  6 Feb 2008 13:12:26 -0000       1.208.2.4
@@ -265,7 +265,7 @@
 this lock guards the swap (loaded/unloaded) status of the BATs. Hence, all
 BBP routines that influence the swapping policy, or actually carry out the
 swapping policy itself, acquire this lock (e.g. @emph{BBPfix},@emph{BBPunfix}).
-Note that this also means that updates to the BBP\_status indicator array
+Note that this also means that updates to the BBP_status indicator array
 must be protected by GDKswapLock. 
 
 To reduce contention GDKswapLock was split into multiple locks; it is now 
@@ -1794,7 +1794,7 @@
 to avoid further deadlock, the update functions in BBP that hold either 
 GDKcacheLock or a GDKswapLock may never cause a BBPtrim (notice that BBPtrim 
 could theoretically be set off just by allocating a little piece of memory, 
e.g. 
-GDKstrdup()). If these routines must alloc memory, they must set the 
BBP\_notrim 
+GDKstrdup()). If these routines must alloc memory, they must set the 
BBP_notrim 
 variable, acquiring the addition GDKtrimLock, in order to prevent such 
deadlock.
 @item
 the BBPtrim is atomic; only releases its locks when all BAT unload 

Index: gdk_heap.mx
===================================================================
RCS file: /cvsroot/monetdb/MonetDB/src/gdk/gdk_heap.mx,v
retrieving revision 1.93
retrieving revision 1.93.2.1
diff -u -d -r1.93 -r1.93.2.1
--- gdk_heap.mx 1 Feb 2008 12:21:36 -0000       1.93
+++ gdk_heap.mx 6 Feb 2008 13:12:28 -0000       1.93.2.1
@@ -497,7 +497,7 @@
 As we do not (yet) want to change the BAT image on disk, This is now fixed by 
 switching on-the-fly between two representations. We ensure that the 64-bit 
memory 
 representation is just as long as the 32-bits version (20 bytes) so the rest 
of 
-the heap never needs to shift. The function HEAP\_checkformat converts at load 
+the heap never needs to shift. The function HEAP_checkformat converts at load 
 time dynamically between the layout found on disk and the memory format.
 Recognition of the header mode is done by looking at the first two ints: 
 alignment must be 4 or 8, and head can never be 4 or eight. 

Index: gdk_bat.mx
===================================================================
RCS file: /cvsroot/monetdb/MonetDB/src/gdk/gdk_bat.mx,v
retrieving revision 1.187
retrieving revision 1.187.2.1
diff -u -d -r1.187 -r1.187.2.1
--- gdk_bat.mx  1 Feb 2008 12:21:35 -0000       1.187
+++ gdk_bat.mx  6 Feb 2008 13:12:25 -0000       1.187.2.1
@@ -2476,8 +2476,8 @@
 goto (1)
 @end multitable
 
-Now we see that for BBPsync (heap\_move) it is sufficient to check for the 
.priv
-suffix to determine the appropriate backup\_bat behavior (i.e. register a X 
.killfile
+Now we see that for BBPsync (heap_move) it is sufficient to check for the .priv
+suffix to determine the appropriate backup_bat behavior (i.e. register a X 
.killfile
 anticipating the write(X) besides a X.priv).
 
 HEAPsave: we do not need to worry about saving readonly bats: as we save them 
in 


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Monetdb-checkins mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/monetdb-checkins

Reply via email to