public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@Elf.ucw.cz>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Rik van Riel <riel@conectiva.com.br>,
	Linus Torvalds <torvalds@transmeta.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [POT] Which journalised filesystem ?
Date: Sat, 6 Oct 2001 00:05:27 +0200	[thread overview]
Message-ID: <20011006000527.A1306@elf.ucw.cz> (raw)
In-Reply-To: <E15pWQA-0006bs-00@the-village.bc.nu> <m1669uyuqy.fsf@frodo.biederman.org>
In-Reply-To: <m1669uyuqy.fsf@frodo.biederman.org>

Hi!

> > > > We (as in Linux) should make sure that we explicitly tell the disk when
> > > > we need it to flush its disk buffers. We don't do that right, and
> > > > because of _our_ problems some people claim that writeback caching is
> > > > evil and bad.
> > > 
> > > Does this even work right for IDE ?
> > 
> > Current IDE drives it may be a NOP. Worse than that it would totally ruin
> > high end raid performance. We need to pass write barriers. A good i2o card
> > might have 256Mb of writeback cache that we want to avoid flushing - because
> > it is battery backed and can be ordered.
> 
> If the cache is small and is primarily a track cache (IDE) one trick that
> we can do is to flood the cache with data so everything is forced out.
> 
> We can do this at mkfs time, (so even destructive tests are allowed)
> and we can probe how to make this work for a particular drive.  And
> then the kernel can just use the results of that probe. 

How do you probe this without actually powering system down?

  parent reply	other threads:[~2001-10-06 20:18 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-03 12:00 [POT] Which journalised filesystem uses Linus Torvalds ? sebastien.cabaniols
2001-10-03 12:39 ` [POT] Which journalised filesystem ? Rik van Riel
2001-10-03 12:54   ` Dave Jones
2001-10-03 13:00     ` Billy Harvey
2001-10-04 22:14       ` Alan Cox
2001-10-04 22:14         ` Dave Jones
2001-10-04 22:24           ` Alan Cox
2001-10-03 13:01     ` Ragnar Kjørstad
2001-10-03 13:24       ` Dave Jones
2001-10-03 17:51       ` Andrew Morton
2001-10-03 15:34     ` André Dahlqvist
2001-10-04 21:25       ` Alan Cox
2001-10-04 21:53         ` Alessandro Suardi
2001-10-03 17:03     ` Matthias Andree
2001-10-03 17:40       ` Sujal Shah
2001-10-03 19:13         ` Erik Mouw
2001-10-03 20:52           ` Mark Hahn
2001-10-04 22:49             ` Bernd Eckenfels
2001-10-04 23:27               ` Linus Torvalds
2001-10-04 23:55                 ` Rik van Riel
2001-10-05 14:57                   ` Alan Cox
2001-10-05 15:25                     ` Eric W. Biederman
2001-10-05 20:25                       ` Bernd Eckenfels
2001-10-05 23:41                         ` Miquel van Smoorenburg
2001-10-06  8:32                           ` Tonu Samuel
2001-10-06  9:16                             ` Miquel van Smoorenburg
2001-10-06 16:42                             ` Bernd Eckenfels
2001-10-05 22:05                       ` Pavel Machek [this message]
2001-10-07  0:51                         ` Eric W. Biederman
2001-10-10 17:29                     ` Stephen C. Tweedie
2001-10-05  1:05                 ` Mike Fedyk
2001-10-03 17:41       ` Xavier Bestel
2001-10-03 17:53         ` Matthias Andree
2001-10-03 17:36     ` Stephen C. Tweedie
2001-10-03 17:41       ` Dave Jones
2001-10-04 21:09       ` Alan Cox
2001-10-05 10:27         ` Stephen C. Tweedie
2001-10-03 14:33 ` [POT] Which journalised filesystem uses Linus Torvalds ? Dave Cinege
2001-10-03 14:48   ` Sean Hunter
2001-10-03 16:54 ` Fabbione
2001-10-03 17:52 ` Bernd Eckenfels
2001-10-03 18:01 ` Luigi Genoni
2001-10-04  5:42 ` Andrew Ip
2001-10-04  7:32 ` Constantin Loizides
2001-10-04 16:30 ` Nathan Straz
2001-10-04 17:21   ` Hristo Grigorov

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=20011006000527.A1306@elf.ucw.cz \
    --to=pavel@elf.ucw.cz \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    --cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox