login
Header Space

 
 

Re: HAMMER filesystem update - design document

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <kernel@...>
Date: Thursday, October 11, 2007 - 2:04 am

Matthew Dillon wrote:

Any specific reason not to go with a B+-Tree or B#-Tree which have shown 
to have advantageous effects?

Also, what, if any, will be the locking policy for multiple I/O threads 
accessing a single HAMMER filesystem? Shared/exclusive mutexes on the 
cluster level?

(Whomever invented early mornings does not deserve brownie points),
-- 
         Thomas E. Spanjaard
         tgen@netphreax.net
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
HAMMER filesystem update - design document, Matthew Dillon, (Wed Oct 10, 3:33 pm)
Re: HAMMER filesystem update - design document, Thomas Zander, (Sat Oct 13, 1:24 pm)
Re: HAMMER filesystem update - design document, Francois Tigeot, (Thu Oct 11, 3:22 am)
Re: HAMMER filesystem update - design document, Bill Hacker, (Thu Oct 11, 4:38 am)
Re: HAMMER filesystem update - design document, Michael Neumann, (Thu Oct 11, 3:55 am)
Re: HAMMER filesystem update - design document, Thomas E. Spanjaard, (Thu Oct 11, 2:04 am)
Re: HAMMER filesystem update - design document, Michael Neumann, (Wed Oct 10, 7:12 pm)
Re: HAMMER filesystem update - design document, Michael Neumann, (Thu Oct 11, 4:18 am)
Re: HAMMER filesystem update - design document, Bill Hacker, (Thu Oct 11, 4:49 am)
Re: HAMMER filesystem update - design document, Bill Hacker, (Wed Oct 10, 4:30 pm)
speck-geostationary