Re: Quota file format proposal

Pauline Middelink (middelin@polyware.nl)
Tue, 18 May 1999 08:07:57 +0200

On Mon, May 17, 1999 at 01:48:41PM +0200, Jan Kara wrote:
> Hello.
>
> So 2.3 is out and so we can start implementing new quota file format. My proposal is following:
> struct quota_file_header {
> u32 qfh_Magic;
> u32 qfh_Version;
> };
> qfh_Magic would identify quota file so we can be sure it is really ours... Currently we will use 2 magics
> - for user and for group quota file.
> qfh_Version is I think clear.
>
> struct quota_time_limits {
> u64 qfd_btime;
> u64 qfd_itime;
> };
>
> This entry will specify time limits after which soft-quota becomes hard-quota. Currently this times are
> stored in root's structure but as we are going to have capabilities I think it's better to have nonexeptional
> structure for UID 0.

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...

> struct quota_block {
> u32 qb_curblocks, qb_bhardlimit, qb_bsoftlimit;
> same for inodes
> u64 qb_btime, qb_time;
> };
>
> This is same as it was before except the thing we have 64-bits for time.
> I would propose to have also special structure for inmemory copy of quota_block which would be same as is know -
> ie. time_t for times... Maybe uint for limits?

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...

Met vriendelijke groet,
Pauline Middelink

-- 
PGP Key fingerprint = DE 6B D0 D9 19 AD A7 A0  58 A3 06 9D B6 34 39 E2
For more details look at my website http://www.polyware.nl/~middelin


-
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/