Bryan Henderson wrote: > I think "reservation" is wrong for one of them and anyone using it that > way should stop.
Hehe, start with ext3 :-) > I believe the common terminology is: Sounds reasonable. The thing with "reservation" is that people use it in daily life with all kinds of meanings, and often with the object of the reservation, e.g. "reserve a seat" (typically a specific seat), "reserve some time" (often not a specific interval), or "reserve a table" (at a restaurant, you don't know which one, but the restaurant staff does). To muddy the issue further, reservations can be more or less firm. E.g. if we "reserve" the next hundred blocks, so that allocation is contiguous, we may want to be able to take them away if some other file needs them. On the other hand, if storage is already committed, but just not on disk yet, that reservation shouldn't be revokable. - Werner -- _________________________________________________________________________ / Werner Almesberger, Buenos Aires, Argentina [EMAIL PROTECTED] / /_http://www.almesberger.net/____________________________________________/ - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
