mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "\"Портон Виктор Львович\"" <porton@yandex.ru>
To: 7eggert@gmx.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: MTD for buffered IO
Date: Tue, 14 Feb 2006 01:59:27 +0300 (MSK)	[thread overview]
Message-ID: <43F10F4F.000002.27180@webmail9.yandex.ru> (raw)
In-Reply-To: <E1F8dq8-0000oW-N2@be1.lrz>



> Victor Porton,,, <porton@ex-code.com> wrote:
> 
> > I suggest to add kernel configuration/option to allow to use
> > an MTD device as a continuation of I/O buffers (for HDD).
> 
> Why do you want to be limited to MTD devices?
> What about creating a device-mapper target using JBD instead?

Good idea, which probably already works with current Linux with ext3. But we should be not limited to JDB systems. Your idea works only with JDB, so your idea (despite of being a good idea) is a hack.

> > One way to implement it would be to add the option for a swap
> partition/file
> > to allow to use this swap partition/file as I/O buffer for other device.
> 
> -EBADIDEA. You'd certainly lose data on power failures.

How it is worse than to lose data on power failures with the standard Linux memory I/O cache?

Moreover so we can lose LESS, as Flash memory will preserve swap content unlike RAM.

> -- 
> Ich danke GMX dafьr, die Verwendung meiner Adressen mittels per SPF
> verbreiteten Lьgen zu sabotieren.
> 

-- 
Victor Porton (porton@ex-code.com)

       reply	other threads:[~2006-02-13 22:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5FIFF-2PL-39@gated-at.bofh.it>
     [not found] ` <E1F8dq8-0000oW-N2@be1.lrz>
2006-02-13 22:59   ` "Портон Виктор Львович" [this message]
2006-02-17 11:53     ` Bodo Eggert
2006-02-13  9:08 Victor Porton,,,
2006-02-13 13:39 ` Josh Boyer

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=43F10F4F.000002.27180@webmail9.yandex.ru \
    --to=porton@yandex.ru \
    --cc=7eggert@gmx.de \
    --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®