From: Eric Sandeen <sandeen@sandeen.net>
To: markgw@sgi.com
Cc: Russell Cattelan <cattelan@thebarn.com>,
nscott@aconex.com, Barry Naujok <bnaujok@sgi.com>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: [REVIEW] Don't make lazy counters default for mkfs
Date: Fri, 29 Feb 2008 18:11:03 -0600 [thread overview]
Message-ID: <47C89F17.7040307@sandeen.net> (raw)
In-Reply-To: <47C89B94.4060002@sandeen.net>
Eric Sandeen wrote:
> maybe just 2 values, with the actual supported features (& features2)
> values anded together? Easy enough to parse in the code.
>
> i.e.
>
> # cat /proc/fs/xfs/features
> 0xffffffff
> 0x00000001
hm, but of course mkfs should never be checking for anything in the
first features slot; yesterday's kernels support all those flags but
don't export anything.
wow, this is starting to feel as complex as ext4's flags ;)
-Eric
next prev parent reply other threads:[~2008-03-01 0:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 1:09 [REVIEW] Don't make lazy counters default for mkfs Barry Naujok
2008-02-28 2:35 ` Nathan Scott
2008-02-29 21:21 ` Russell Cattelan
2008-02-29 23:11 ` Eric Sandeen
2008-02-29 23:19 ` Russell Cattelan
2008-02-29 23:47 ` Mark Goodwin
2008-02-29 23:56 ` Eric Sandeen
2008-03-01 0:11 ` Eric Sandeen [this message]
2008-03-02 23:59 ` Barry Naujok
2008-03-01 0:02 ` Josef 'Jeff' Sipek
2008-03-02 23:34 ` Nathan Scott
2008-03-03 0:16 ` Timothy Shimmin
2008-03-03 0:30 ` Mark Goodwin
2008-03-03 1:15 ` Josef 'Jeff' Sipek
2008-03-03 3:56 ` Eric Sandeen
2008-03-03 4:14 ` Josef 'Jeff' Sipek
2008-03-03 4:19 ` Eric Sandeen
2008-03-03 4:47 ` Niv Sardi
2008-03-03 0:18 ` Donald Douwsma
2008-03-03 0:24 ` Nathan Scott
2008-03-02 10:26 ` Andi Kleen
2008-03-02 10:41 ` Josef 'Jeff' Sipek
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=47C89F17.7040307@sandeen.net \
--to=sandeen@sandeen.net \
--cc=bnaujok@sgi.com \
--cc=cattelan@thebarn.com \
--cc=markgw@sgi.com \
--cc=nscott@aconex.com \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.