mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Peter T. Breuer" <ptb@it.uc3m.es>
To: Anton Altaparmakov <aia21@cantab.net>
Cc: "Peter T. Breuer" <ptb@it.uc3m.es>,
	Daniel Phillips <phillips@arcor.de>,
	Alexander Viro <viro@math.psu.edu>,
	Xavier Bestel <xavier.bestel@free.fr>,
	david.lang@digitalinsight.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: (fwd) Re: [RFC] mount flag "direct"
Date: Fri, 6 Sep 2002 11:17:05 +0200 (MET DST)	[thread overview]
Message-ID: <200209060917.g869H5c08220@oboe.it.uc3m.es> (raw)
In-Reply-To: <5.1.0.14.2.20020906100358.03ed0bf0@pop.cus.cam.ac.uk> from Anton Altaparmakov at "Sep 6, 2002 10:08:47 am"

"Anton Altaparmakov wrote:"
> At 09:57 06/09/02, Peter T. Breuer wrote:
> >"Anton Altaparmakov wrote:"
> >I've had a look now. I concur that e2fs at least is full of assumptions
> >that it has various different sorts of metadata in memory at all times.
> >I can't rewrite that, or even add a "warning will robinson" callback to
> >vfs, as I intended. What I can do, I think, is ..
> 
> Oh, you saw the light. (-: I can assure you that most file systems make 

The question is if they do it in a way I can read. If I can read it, I
can fix it. There was too much noise inside e2fs to see a point or points
of intercept. So the intercept has to be higher, and ..

> direct_IO, I plan to keep all metadata caching in place, just stop caching 
> the actual file data. That should give maximum performance I think.

But not correct behaviour wrt metadata in a shared disk fs. And your
calculation of "maximum performance" is off. Look, you seem to forget
this:

   suppose that I make the FS twice as slow as before by meddling with
   it to make it sharable

   then I simply share it among 4 nodes to get a two times _speed up_
   overall.

That's the basic idea. Details left to reader.

I.e. I don't care if it gets slower. We are talking thousands of nodes
here. Only the detail of the topology is affected by the real numbers.

> >.. simply do a dput of the fs root directory from time to time, from
> >vfs - whenever I think it is appropriate. As far as I can see from my
> >quick look that may cause the dcache path off that to be GC'ed. And
> >that may be enough to do a few experiments for O_DIRDIRECT.
> 
> What does "GC" mean?

Garbage collection. I assume that either there is a point at which the
dcache is swept or as I free a dentry from the cache its dependents
are swept. I don't know which. Feel free to enlighten me. My question
is simply "is doing a dput of the base directory dentry on the FS
enough to clear the dcache for that FS"?

Peter

  reply	other threads:[~2002-09-06  9:12 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-03 21:48 Peter T. Breuer
2002-09-03 22:19 ` Anton Altaparmakov
2002-09-03 22:42   ` Peter T. Breuer
2002-09-03 22:52     ` Xavier Bestel
2002-09-03 23:44       ` Peter T. Breuer
2002-09-04  7:06         ` Alexander Viro
2002-09-04  9:02           ` Peter T. Breuer
2002-09-04 11:05             ` Anton Altaparmakov
2002-09-04 11:39               ` Peter T. Breuer
2002-09-04 14:13                 ` Anton Altaparmakov
2002-09-05 22:45                   ` Daniel Phillips
2002-09-05 23:06                     ` Anton Altaparmakov
2002-09-05 23:17                       ` Daniel Phillips
2002-09-05 23:24                         ` Anton Altaparmakov
2002-09-06  8:57                           ` Peter T. Breuer
2002-09-06  9:08                             ` Anton Altaparmakov
2002-09-06  9:17                               ` Peter T. Breuer [this message]
2002-09-06  9:50                                 ` Lars Marowsky-Bree
2002-09-06 14:10                                   ` Peter T. Breuer
2002-09-06 13:20                                 ` Helge Hafting
2002-09-06 13:22                                 ` Rik van Riel
2002-09-06 13:53                                   ` Peter T. Breuer
2002-09-06 15:32                                     ` Rik van Riel
2002-09-06 14:25                       ` Peter T. Breuer
2002-09-06 17:20                         ` Anton Altaparmakov
2002-09-06 17:33                           ` Daniel Phillips
2002-09-06 19:32                             ` Anton Altaparmakov
2002-09-06 18:29                           ` Peter T. Breuer
2002-09-06 19:30                             ` Anton Altaparmakov
2002-09-09 16:30                           ` Peter T. Breuer
2002-09-17 11:21                             ` Anton Altaparmakov
2002-09-05  8:30                 ` Helge Hafting
2002-09-05  8:43                   ` David Lang
2002-09-05 14:24                   ` Peter T. Breuer
2002-09-05 16:59                     ` David Lang
2002-09-05 23:08                     ` Daniel Phillips
2002-09-06  8:14                     ` Ingo Oeser
2002-09-06  9:06                     ` Helge Hafting
2002-09-04 12:49             ` Ragnar Kjørstad
2002-09-04 12:54               ` Peter T. Breuer
2002-09-04 13:22                 ` Ragnar Kjørstad
2002-09-05  3:36                 ` Edgar Toernig
2002-09-05  3:58                   ` Alexander Viro
2002-09-05 15:59                     ` [RFC] intent-based lookup (was: mount flag "direct") Andreas Dilger
2002-09-03 23:24     ` (fwd) Re: [RFC] mount flag "direct" David Lang
2002-09-04  4:27   ` Kevin O'Connor
2002-09-03 23:05 ` David Lang
     [not found] <02Sep6.161154edt.62237@gpu.utcc.utoronto.ca>
2002-09-07 13:36 ` Peter T. Breuer
     [not found] <20020909181724.GA31153@ravel.coda.cs.cmu.edu>
2002-09-09 18:58 ` 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=200209060917.g869H5c08220@oboe.it.uc3m.es \
    --to=ptb@it.uc3m.es \
    --cc=aia21@cantab.net \
    --cc=david.lang@digitalinsight.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@arcor.de \
    --cc=viro@math.psu.edu \
    --cc=xavier.bestel@free.fr \
    /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®