mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Charles Manning <manningc2@actrix.gen.nz>
To: Valdis.Kletnieks@vt.edu
Cc: cdhmanning@gmail.com, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/9] Add yaffs Kconfig and Makefile
Date: Mon, 8 Nov 2010 09:59:35 +1300	[thread overview]
Message-ID: <201011080959.35220.manningc2@actrix.gen.nz> (raw)
In-Reply-To: <10039.1289008258@localhost>

On Saturday 06 November 2010 14:50:58 Valdis.Kletnieks@vt.edu wrote:
> On Thu, 04 Nov 2010 05:53:16 +1300, cdhmanning@gmail.com said:
> > From: Charles Manning <cdhmanning@gmail.com>
> >
> > Adding yaffs2 file system.
> >
> > +config YAFFS_DOES_ECC
> > +	bool "Lets Yaffs do its own ECC"
> > +	depends on YAFFS_FS && YAFFS_YAFFS1 && !YAFFS_9BYTE_TAGS
> > +	default n
> > +	help
> > +	  This enables Yaffs to use its own ECC functions instead of using
> > +	  the ones from the generic MTD-NAND driver.
> > +
> > +	  If unsure, say N.
>
> Why does this exist at all? Are there any cases where the Yaffs ECC is
> better than the MTD versions? If so, why aren't we fixing the MTD versions?

Good point. I'll look into this further.

This came into existence when mtd had various issues that were easier to 
address in yaffs space than mtd space.

>
> > +config YAFFS_DISABLE_TAGS_ECC
> > +	bool "Disable YAFFS from doing ECC on tags by default"
> > +	depends on YAFFS_FS && YAFFS_YAFFS2
> > +	default n
> > +	help
> > +	  This defaults Yaffs to using its own ECC calculations on tags instead
> > of +	  just relying on the MTD.
> > +	  This behavior can also be overridden with tags_ecc_on and
> > +	  tags_ecc_off mount options.
> > +
> > +	  If unsure, say N.
>
> Similarly here - why would somebody want this?

This is quite a different issue.
Most hamming code ecc schemes only do ecc on the data area and not on the 
oob/spare area where yaffs stores tags,but some do.

This config controls which way the ECC on the tags is handled.

>
> > +config YAFFS_EMPTY_LOST_AND_FOUND
> > +	bool "Empty lost and found on boot"
> > +	depends on YAFFS_FS
> > +	default n
> > +	help
> > +	  If this is enabled then the contents of lost and found is
> > +	  automatically dumped at mount.
>
> Wow.. Just.. wow.   

What does that mean?

> Under what use case is this a good idea for a config 
> option as opposed to a mount option?

It is both.

Providing a config option provides the system integrator with flexibility in 
how they set things up.

-- Charles

  reply	other threads:[~2010-11-07 20:59 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-03 16:53 [PATCH 0/9] Add yaffs2 file system cdhmanning
2010-11-03 16:53 ` [PATCH 1/9] Add yaffs Kconfig and Makefile cdhmanning
2010-11-03 17:46   ` Greg KH
2010-11-03 17:55     ` David Daney
2010-11-03 18:06       ` Greg KH
2010-11-04 20:58     ` Charles Manning
2010-11-04 22:36       ` Greg KH
2010-11-05  0:14         ` Ryan Mallon
2010-11-06  1:50   ` Valdis.Kletnieks
2010-11-07 20:59     ` Charles Manning [this message]
2010-11-07 21:45       ` Chris Snook
2010-11-07 22:22         ` Charles Manning
2010-11-08 10:24           ` Chris Snook
2010-11-08 21:22             ` Charles Manning
2010-11-08 22:15               ` Chris Snook
2010-11-03 16:53 ` [PATCH 2/9] Add yaffs allocator, bitmap and attrib source cdhmanning
2010-11-04 23:01   ` Jesper Juhl
2010-11-07 22:42     ` Charles Manning
2010-11-03 16:53 ` [PATCH 3/9] Add yaffs checkpointing, blockinfo, nameval and os context cdhmanning
2010-11-03 16:53 ` [PATCH 4/9] Add yaffs ecc, mtd access and nand abstraction code cdhmanning
2010-11-03 17:05   ` David Daney
2010-11-03 16:53 ` [PATCH 5/9] Add yaffs_guts.c cdhmanning
2010-11-03 16:53 ` [PATCH 6/9] Add some yaffs include files cdhmanning
2010-11-03 17:10   ` David Daney
2010-11-03 17:16     ` Charles Manning
2010-11-09 17:12   ` Arnd Bergmann
2010-11-03 16:53 ` [PATCH 7/9] Add yaffs tag access code cdhmanning
2010-11-03 17:16   ` David Daney
2010-11-03 17:17   ` Paulo Marques
2010-11-03 16:53 ` [PATCH 8/9] Add yaffs verification and version specific code cdhmanning
2010-11-03 16:53 ` [PATCH 9/9] Add yaffs kernel glue cdhmanning
2010-11-09 16:57   ` Arnd Bergmann

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=201011080959.35220.manningc2@actrix.gen.nz \
    --to=manningc2@actrix.gen.nz \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=cdhmanning@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®