Home » Mailing list archives » tux3 » 2008 » July » 27

[Tux3] forward logging and NVRAM

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
[view in full thread]
From: timothy norman huber <timothyhuber@...>
To: <tux3@...>
Subject: [Tux3] forward logging and NVRAM
Date: Sunday, July 27, 2008 - 5:10 pm

--Boundary_(ID_FfFe0sYv87fsuz7k+LokDw)

Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes

Content-transfer-encoding: 7BIT


Daniel,


Several weeks ago, during a discussion over coffee, you mentioned a

rather intriguing optimization- by writing the start of the forward

log chain to NVRAM rather than disk, you avoid a disk seek and write

transfer for each forward log chain.  i believe there was another

motivation that had to do with avoiding traversing the entire volume

in case of a crash.  Was this design feature to overcome lame fsck

performance?


T


Timothy Huber

Strategic Account Development


tim.huber@metaram.com

cell 310 795.6599


MetaRAM Inc.

181 Metro Drive, Suite 400

San Jose, CA 95110


http://www.linkedin.com/in/timhuber


--Boundary_(ID_FfFe0sYv87fsuz7k+LokDw)

Content-type: text/html; charset=US-ASCII

Content-transfer-encoding: quoted-printable


Daniel,
Several weeks ago, during a =

discussion over coffee, you mentioned a rather intriguing optimization- =

by writing the start of the forward log chain to NVRAM rather than disk, =

you avoid a disk seek and write transfer for each forward log chain. =

 i believe there was another motivation that had to do with =

avoiding traversing the entire volume in case of a crash.  Was this =

design feature to overcome lame fsck performance? =

 
T

 Timothy =

HuberStrategic Account =

Development
tim.huber@metaram.comcell 310 =

795.6599
MetaRAM =

Inc.181 Metro Drive, Suite 400 San Jose, CA 95110 
http://www.linkedin.com/in/ti=

mhuber 
=


--Boundary_(ID_FfFe0sYv87fsuz7k+LokDw)--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
Messages in current thread:
[Tux3] [PATCH 1/3] Use tuxtime() to update timestamp, OGAWA Hirofumi, (Tue Nov 11, 1:34 am)
[Tux3] forward logging and NVRAM, timothy norman huber, (Sun Jul 27, 5:10 pm)
[Tux3] [PATCH 2/3] Convert more timestamp to high resolution..., OGAWA Hirofumi, (Tue Nov 11, 1:35 am)
[Tux3] [PATCH 3/3] Add billionths() and use it, instead of m..., OGAWA Hirofumi, (Tue Nov 11, 1:35 am)
Re: [Tux3] forward logging and NVRAM, Daniel Phillips, (Sun Jul 27, 5:29 pm)
Re: [Tux3] forward logging and NVRAM, Maciej Żenczykowski, (Tue Jul 29, 2:06 pm)