From: Christoph Hellwig <hch@infradead.org>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Mingming Cao <cmm@us.ibm.com>,
Badari Pulavarty <pbadari@us.ibm.com>,
Ram Pai <linuxram@us.ibm.com>
Subject: Re: [Patch 2/6]: ext3 reservations: Renumber the ext3 reservations ioctls
Date: Thu, 9 Sep 2004 18:57:02 +0100 [thread overview]
Message-ID: <20040909185702.A13111@infradead.org> (raw)
In-Reply-To: <1094636497.1985.20.camel@sisko.scot.redhat.com>; from sct@redhat.com on Wed, Sep 08, 2004 at 10:41:38AM +0100
On Wed, Sep 08, 2004 at 10:41:38AM +0100, Stephen C. Tweedie wrote:
> Hi,
>
> On Tue, 2004-09-07 at 23:53, Christoph Hellwig wrote:
>
> > Maybe you could reuse the XFS reservation ioctls instead of adding
> > another set? Having incompatible APIs for the same thing on different
> > filesystems sounds like the wrong way to go.
>
> I don't mind either way. But I just looked, and I think they are doing
> different things. If I'm reading the XFS bits right, the XFS ioctls
> actively reserve/free disk space; but the ext3 ones do nothing except
> set/query the size of the per-inode sliding reservation window.
>
> So sounds like they are best kept separate for now.
makes sense.
prev parent reply other threads:[~2004-09-09 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-07 13:02 [Patch 2/6]: ext3 reservations: Renumber the ext3 reservations ioctls Stephen Tweedie
2004-09-07 22:53 ` Christoph Hellwig
2004-09-08 9:41 ` Stephen C. Tweedie
2004-09-09 17:57 ` Christoph Hellwig [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040909185702.A13111@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=cmm@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=pbadari@us.ibm.com \
--cc=sct@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox