>> Which structs are 'indexed' by the UID? If the quota_time_limits
>> are only stored once, you could better add them to the header
>> struct to have one header and many quota_blocks...
> The time limits will be there only once.. I just separated them to other structure as I'd like
> to have first header completely implementation independent.. There are also times in quota_block -
> they have to be there as they identify time, when soft quota changes into hard quota.
>> Isn't it possible to code the uid/gid in the struct too, this way
>> we dont have to write a 1GB(?) file for 2 users, one at UID0 and
>> one at UID 131072... Since this struct is read into memory-structs
>> some small handeling shouldn't really matter in performance...
> We won't write 1GB of data. We take advantage of sparse files so there is almost no
> difference between storage of UIDS 1000, 1010 and 1000, 10000...
> Honza.
Wouldn't it be a good idea at this point to switch to a more flexible
format for the quota file? You are correct with the above remarks as
long as userids stay 2 bytes long. For 4 byte userids we are above the
limit for the current maximum file size of ext2 with respect to the
quota file. What about using a hash table instead?
--Joerg Lenneis
email: lenneis@statrix2.wu-wien.ac.at
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/