mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Peter T. Breuer" <ptb@it.uc3m.es>
To: David Lang <david.lang@digitalinsight.com>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] mount flag "direct"
Date: Tue, 3 Sep 2002 19:30:18 +0200 (MET DST)	[thread overview]
Message-ID: <200209031730.g83HUIb15556@oboe.it.uc3m.es> (raw)
In-Reply-To: <Pine.LNX.4.44.0209031003370.1889-100000@dlang.diginsite.com> from David Lang at "Sep 3, 2002 10:07:48 am"

"A month of sundays ago David Lang wrote:"
> Peter, the thing that you seem to be missing is that direct mode only
> works for writes, it doesn't force a filesystem to go to the hardware for
> reads.

Yes it does. I've checked! Well, at least I've checked that writing
then reading causes the reads to get to the device driver. I haven't
checked what reading twice does.

If it doesn't cause the data to be read twice, then it ought to, and
I'll fix it (given half a clue as extra pay ..:-)

> for many filesystems you cannot turn off their internal caching of data
> (metadata for some, all data for others)

Well, let's take things one at a time. Put in a VFS mechanism and then
convert some FSs to use it.

> so to implement what you are after you will have to modify the filesystem
> to not cache anything, since you aren't going to do this for every

Yes.

> filesystem you end up only haivng this option on the one(s) that you
> modify.

I intend to make the generic mechanism attractive.

> if you have a single (or even just a few) filesystems that have this
> option you may as well include the locking/syncing software in them rather
> then modifying the VFS layer.

Why? Are you advocating a particular approach? Yes, I agree that that
is a possible way to go - but I will want the extra VFS ops anyway, 
and will want to modify the particular fs to use them, no?

Peter

  reply	other threads:[~2002-09-03 17:25 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-03 15:01 Peter T. Breuer
2002-09-03 15:13 ` Rik van Riel
2002-09-03 15:53   ` Maciej W. Rozycki
2002-09-03 16:04     ` Peter T. Breuer
2002-09-03 16:08       ` Rik van Riel
2002-09-03 15:16 ` jbradford
2002-09-03 15:37 ` Anton Altaparmakov
2002-09-03 15:44   ` Peter T. Breuer
2002-09-03 16:23     ` Lars Marowsky-Bree
2002-09-03 16:41       ` Peter T. Breuer
2002-09-03 17:07         ` David Lang
2002-09-03 17:30           ` Peter T. Breuer [this message]
2002-09-03 17:40             ` David Lang
2002-09-04  5:57             ` Helge Hafting
2002-09-04  6:21               ` Peter T. Breuer
2002-09-04  6:49                 ` Helge Hafting
2002-09-04  9:15                   ` Peter T. Breuer
2002-09-04 11:34                     ` Helge Hafting
2002-09-03 17:26         ` Rik van Riel
2002-09-03 18:02           ` Andreas Dilger
2002-09-03 18:44             ` Daniel Phillips
2002-09-03 17:29         ` Jan Harkes
2002-09-03 18:31         ` Daniel Phillips
2002-09-03 18:20     ` Daniel Phillips
     [not found] <20020907164631.GA17696@marowsky-bree.de>
2002-09-07 19:59 ` [lmb@suse.de: Re: [RFC] mount flag "direct" (fwd)] Peter T. Breuer
2002-09-07 21:14   ` [RFC] mount flag "direct" Lars Marowsky-Bree
2002-09-08  9:23     ` Peter T. Breuer
2002-09-08  9:59       ` Lars Marowsky-Bree
2002-09-08 16:46         ` Peter T. Breuer

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=200209031730.g83HUIb15556@oboe.it.uc3m.es \
    --to=ptb@it.uc3m.es \
    --cc=david.lang@digitalinsight.com \
    --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®