xfs
[Top] [All Lists]

Re: [PATCH 0/4] quota: add new quotactl Q_XGETQUOTA2

To: Jan Kara <jack@xxxxxxx>
Subject: Re: [PATCH 0/4] quota: add new quotactl Q_XGETQUOTA2
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Mon, 18 Jan 2016 09:18:16 -0600
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>, fsdevel <linux-fsdevel@xxxxxxxxxxxxxxx>, Eric Sandeen <sandeen@xxxxxxxxxx>, xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20160118103302.GD6850@xxxxxxxxxxxxx>
References: <568FEA2C.6080708@xxxxxxxxxx> <20160109072600.GA21636@xxxxxxxxxxxxx> <20160111132617.GD6262@xxxxxxxxxxxxx> <5693D33A.5090307@xxxxxxxxxxx> <20160111162807.GK6262@xxxxxxxxxxxxx> <5696D27A.9070700@xxxxxxxxxxx> <20160115093507.GA15950@xxxxxxxxxxxxx> <56992CD4.6030408@xxxxxxxxxxx> <20160118103302.GD6850@xxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
On 1/18/16 4:33 AM, Jan Kara wrote:
> On Fri 15-01-16 11:31:00, Eric Sandeen wrote:

...

>> For a purpose-built interface of "find the next ID" that wouldn't require any
>> structure or interface changes...
>>
>> We could name it Q_GETNEXTQUOTA / Q_XGETNEXTQUOTA to make it explicit about
>> the purpose, and document that return behavior.  Done & done.  ;)
>>
>> A new grand unified extensible quota call sounds like a great idea, I just
>> hate to gate this work on designing a brand-new interface.
> 
> OK, ok. I like Dave's proposal for quotactl2(). So let's leave the unification
> for later and implent Q_GETNEXTQUOTA and Q_XGETNEXTQUOTA with the
> functionality of your original Q_XGETQUOTA2. Having separate call to get
> next ID would save us one new quotactl but OTOH we would need two syscalls
> (and quota structure lookups) to report one structure and there are
> potentially *lots* of them.

Ok, I can re-do it with the new Q_[X]GETNEXTQUOTA names, I've already done
the non-xfs one as well, just starting testing on that.

With or without the flags argument?

Thanks,
-Eric

<Prev in Thread] Current Thread [Next in Thread>