From: Chuck Ebbert <cebbert.lkml@gmail.com>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>
Cc: Albino B Neto <bino@riseup.net>,
Raymond Jennings <shentino@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jan Kara <jack@suse.cz>, LKML <linux-kernel@vger.kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [GIT PULL] Ext3 removal, quota & udf fixes
Date: Wed, 2 Sep 2015 07:58:20 -0400 [thread overview]
Message-ID: <20150902075821.53108f0e@as> (raw)
In-Reply-To: <55E5FF01.2000304@gmail.com>
On Tue, 1 Sep 2015 15:39:45 -0400
Austin S Hemmelgarn <ahferroin7@gmail.com> wrote:
> On 2015-09-01 06:29, Albino B Neto wrote:
> > 2015-08-31 19:31 GMT-03:00 Raymond Jennings <shentino@gmail.com>:
> >> I think also that we should remove the ext2 driver before we remove the ext3
> >> driver.
> >
> > Yes. It is logical to remove the old ext2 drive, because there are
> > more computers with ext3 that ext2. Ext2 is obsolete by existing
> > technologies.
> >
> NO, it is not logical. A vast majority of Android smartphones in the
> wild use ext2, as do a very significant portion of embedded systems that
> don't have room for the few hundred kilobytes of extra code that the
> ext4 driver has in comparison to ext2.
Would it be possible to discard the code used for ext4 and ext3
features at module init time? So you could do something like:
modprobe ext4 no_ext4 no_ext3
and all the space used by those functions would be freed and the
filesystem driver would mark all the ext3/ext4 features as
unsupported.
next prev parent reply other threads:[~2015-09-02 11:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 6:19 [GIT PULL] Ext3 removal, quota & udf fixes Jan Kara
2015-08-31 21:37 ` Linus Torvalds
2015-08-31 22:31 ` Raymond Jennings
2015-08-31 22:39 ` Linus Torvalds
2015-08-31 23:03 ` Raymond Jennings
2015-09-01 2:53 ` Theodore Ts'o
2015-09-01 12:52 ` Eric Sandeen
2015-09-01 15:17 ` Jeff Mahoney
2015-09-01 0:24 ` Raymond Jennings
2015-09-01 6:44 ` Christoph Hellwig
2015-09-01 10:29 ` Albino B Neto
2015-09-01 19:39 ` Austin S Hemmelgarn
2015-09-01 23:58 ` Theodore Ts'o
2015-09-02 16:58 ` Austin S Hemmelgarn
2015-09-02 3:30 ` Albino B Neto
2015-09-02 5:46 ` Raymond Jennings
2015-09-02 13:28 ` Austin S Hemmelgarn
2015-09-02 11:58 ` Chuck Ebbert [this message]
2015-09-02 13:33 ` Austin S Hemmelgarn
2015-09-01 0:23 ` Andreas Dilger
2015-09-02 16:52 ` Mel Gorman
2015-09-02 18:45 ` Darrick J. Wong
2015-09-02 23:47 ` Linus Torvalds
2015-09-03 11:28 ` Albino B Neto
2015-09-03 21:49 ` Darrick J. Wong
2015-09-15 5:31 ` Jan Kara
2015-09-03 18:22 ` Richard Yao
2015-09-03 18:36 ` Eric Sandeen
2015-09-03 19:13 ` Richard Yao
2015-09-03 18:36 ` Darrick J. Wong
2015-09-03 19:16 ` Richard Yao
2015-09-03 19:36 ` Darrick J. Wong
2015-09-03 22:26 ` Richard Yao
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=20150902075821.53108f0e@as \
--to=cebbert.lkml@gmail.com \
--cc=ahferroin7@gmail.com \
--cc=bino@riseup.net \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shentino@gmail.com \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).