mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nathan Scott" <nathans@wobbly.melbourne.sgi.com>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Jan Kara <jack@suse.cz>,
	jank@redhat.com, Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-xfs@oss.sgi.com
Subject: Re: Quota mods needed for journaled quota
Date: Fri, 27 Oct 2000 10:03:19 -0400	[thread overview]
Message-ID: <10010271003.ZM95697@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: "Stephen C. Tweedie" <sct@redhat.com> "Re: Quota mods needed for journaled quota" (Oct 26, 11:00am)
In-Reply-To: <20001025184239.U6085@redhat.com>  <sct@redhat.com>  <10010261253.ZM84523@wobbly.melbourne.sgi.com>  <20001026110029.K20050@redhat.com>

hi Stephen,

On Oct 26, 11:00am, Stephen C. Tweedie wrote:
> Subject: Re: Quota mods needed for journaled quota
> ...
> > This would allow ext3 to do that which it needs to do differently
> > at Q_QUOTAON and would also allow Jan's changes to work in such
> > a way that both the current form of dquot structure and his new
> > version of dquots could be used together
> 
> Adding the init_quota hook would do that, as the filesystem will be
> able to install its own dq_ops methods during the init so we get the
> flexibility you are asking for anyway.
> 

Hmmm ... I'm not so sure.  In order to have the flexibility
of filesystem-specific dquot formats, the struct dquot would
need to become more like struct inode/super_block, i.e. not
hardcoding the ondisk structure into the incore structure
(using a union and a generic pointer, as inode/super_block do).

The DQUOT_SYNC mechanism would need to be able to be overridden
per-filesystem also.  It isn't really as cut-and-dried as "per-
filesystem" either, because an ext2/3 filesystem might make use
of either the original dquot format or Jan's newer format, either
at mount time or even after doing a quota_off & quota_on with a
new quota file format (that would be quite clean).

But I've sidetracked completely from what you were originally
talking about now, which had nothing to do with a different
ondisk format at all.

cheers.

-- 
Nathan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-10-26 23:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20001025184239.U6085@redhat.com>
2000-10-26 16:53 ` Nathan Scott
     [not found]   ` <20001026110029.K20050@redhat.com>
2000-10-27 14:03     ` Nathan Scott [this message]
2000-10-31 15:25       ` Jan Kara
2000-10-31 15:09 ` Jan Kara

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=10010271003.ZM95697@wobbly.melbourne.sgi.com \
    --to=nathans@wobbly.melbourne.sgi.com \
    --cc=jack@suse.cz \
    --cc=jank@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=sct@redhat.com \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®