linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Jörn Engel" <joern@logfs.org>
Cc: David Brown <lkml@davidb.org>, Phil Oester <kernel@linuxace.com>,
	Kay Sievers <kay.sievers@vrfy.org>,
	Phillip Lougher <phillip@lougher.demon.co.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	Christoph Hellwig <hch@infradead.org>,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [GIT PULL] Squashfs pull request for 2.6.29
Date: Sat, 10 Jan 2009 13:43:35 +0100	[thread overview]
Message-ID: <20090110124335.GB30744@elte.hu> (raw)
In-Reply-To: <20090109211937.GA14342@logfs.org>


* Jörn Engel <joern@logfs.org> wrote:

> On Fri, 9 January 2009 11:37:39 -0800, David Brown wrote:
> > On Fri, Jan 09, 2009 at 05:54:22PM +0100, Jörn Engel wrote:
> > >
> > > In general, filesystems and ABI changes are special because stupid 
> > > mistakes are eternal.  If some device driver has a bug, you can fix 
> > > it, reboot and be done with it.  Not so with filesystems.
> > 
> > Squashfs is readonly from the kernel.  The images are created with 
> > userspace tools.
> 
> While true, it doesn't make a difference.  If, for example, your 
> structures members are not naturally aligned, you take a performance hit 
> for no good reason.  Simply moving fields around would make the code go 
> faster.  But the format is fixed and prevents you from making this 
> change.
> 
> You have to get those things right from the beginning or pay for your 
> mistakes everafter.  In general (and I stress "In general") filesystems 
> want more review than ordinary device drivers.  And just to stress that 
> again, this is not an argument against merging squashfs now.

What does a performance hit have to do with an ABI? Absolutely nothing - 
if such a bug is noticed it is fixed, that's it. Your argument does not 
parse and makes absolutely zero technical sense.

Your "ABI is forever" objection against a _read only_ filesystem is a 
newbie mistake worthy of cookie file inclusion - i had a real good laugh 
when i read it ;-)

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-01-10 12:43 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 16:48 [GIT PULL] Squashfs pull request for 2.6.29 Phillip Lougher
2009-01-08 16:50 ` Christoph Hellwig
2009-01-08 17:05   ` Phillip Lougher
2009-01-08 17:11   ` Geert Uytterhoeven
2009-01-08 23:55   ` H. Peter Anvin
2009-01-09  1:53   ` Andrew Morton
2009-01-09  2:11     ` Phillip Lougher
2009-01-09  2:24       ` Kay Sievers
2009-01-09  2:36         ` Phil Oester
2009-01-09 16:54           ` Jörn Engel
2009-01-09 19:37             ` David Brown
2009-01-09 21:19               ` Jörn Engel
2009-01-10 12:43                 ` Ingo Molnar [this message]
2009-01-10 16:50                   ` Jörn Engel
2009-01-10 18:12                     ` Andrew Morton
2009-01-10 18:30                       ` Linus Torvalds
2009-01-10 19:57                         ` Jeff Garzik
2009-01-10 20:16                           ` Leon Woestenberg
2009-01-11  6:36                         ` Valdis.Kletnieks
2009-01-10 19:19                       ` Olivier Galibert
2009-01-10 22:15                       ` Ingo Molnar
2009-01-11  9:30                         ` Geert Uytterhoeven
2009-01-11 15:39                           ` Ingo Molnar
2009-01-11 16:30                             ` Greg KH
2009-01-22 21:50                               ` Dave Jones
2009-01-22 21:57                                 ` Randy Dunlap
2009-01-22 22:15                                   ` Greg KH
2009-01-22 21:58                                 ` Greg KH
2009-01-22 22:26                                   ` Ingo Molnar
2009-01-22 22:50                                   ` Kyle McMartin
2009-01-22 23:04                                     ` Greg KH
2009-01-22 23:25                                       ` Evgeniy Polyakov
2009-01-22 23:34                                       ` Kyle McMartin
2009-01-22 23:41                                         ` Ingo Molnar
2009-01-22 23:28                                     ` Evgeniy Polyakov
2009-01-22 22:16                                 ` Ingo Molnar
2009-01-22 22:24                                   ` Pekka Enberg
2009-01-23  0:16                                 ` Andrew Morton
2009-01-23  0:30                                   ` Greg KH
2009-01-09  2:30     ` Harvey Harrison
2009-01-09 11:25     ` KOSAKI Motohiro
2009-01-09 12:02     ` Alan Cox
2009-01-09 21:56       ` Linus Torvalds
2009-01-09 22:08         ` Andrew Morton
2009-01-09 22:12           ` Linus Torvalds
2009-01-09 22:26             ` Alan Cox
2009-01-09 22:36               ` Harvey Harrison
2009-01-11  3:01         ` Phillip Lougher
2009-01-11  3:06           ` H. Peter Anvin
2009-01-09 16:32     ` Geert Uytterhoeven

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=20090110124335.GB30744@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=joern@logfs.org \
    --cc=kay.sievers@vrfy.org \
    --cc=kernel@linuxace.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@davidb.org \
    --cc=phillip@lougher.demon.co.uk \
    --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).