mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joachim Breuer <jmbreuer@gmx.net>
To: ptb@it.uc3m.es
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] mount flag "direct" (fwd)
Date: Wed, 04 Sep 2002 09:50:37 +0200	[thread overview]
Message-ID: <m38z2i9os2.fsf@venus.fo.et.local> (raw)
In-Reply-To: <200209032107.g83L71h10758@oboe.it.uc3m.es> ("Peter T. Breuer"'s message of "Tue, 3 Sep 2002 23:07:01 +0200 (MET DST)")

"Peter T. Breuer" <ptb@it.uc3m.es> writes:

> "A month of sundays ago Lars Marowsky-Bree wrote:"
>> On 2002-09-03T18:29:02,
>>    "Peter T. Breuer" <ptb@it.uc3m.es> said:
>>
>> > The directory entry would certainly have to be reread after a write
>> > operation on disk that touched it - or more simply, the directory entry
>> > would have to be reread every time it were needed, i.e. be uncached.
>> 
>> *ouch* Sure. Right. You just have to read it from scratch every time. How
>> would you make readdir work?
>
> Well, one has to read it from scratch. I'll set about seeing how to do.
> CLues welcome.

Just an idea, I don't know how well this works what with the 'IDE
can't do write barriers right' and related effects:

- Allow all nodes to cache as many blocks as they wish
- The atomic operation "update this block" includes "invalidate this
  block, if cached" broadcast to all nodes

Performance would certainly become an issue; depending on the
architecture bus sniffing as in certain MP cache consistency protocols
might be feasible (I, node 3, see a transfer from node 1 going to
block #42, which is in my cache; so I update my cache using the data
part of the block transfer as it comes by on the bus).


So long,
   Joe

-- 
"I use emacs, which might be thought of as a thermonuclear
 word processor."
-- Neal Stephenson, "In the beginning... was the command line"

  parent reply	other threads:[~2002-09-04  7:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-03 15:39 Peter T. Breuer
2002-09-03 15:44 ` Rik van Riel
2002-09-03 15:50   ` Peter T. Breuer
2002-09-03 15:56     ` Chris Wedgwood
2002-09-03 15:59       ` Peter T. Breuer
2002-09-03 16:09     ` Richard B. Johnson
2002-09-03 16:29       ` Peter T. Breuer
2002-09-03 16:33         ` Rik van Riel
2002-09-03 17:32         ` Richard B. Johnson
2002-09-03 18:53         ` Lars Marowsky-Bree
2002-09-03 21:07           ` Peter T. Breuer
2002-09-03 21:15             ` Andreas Dilger
2002-09-03 21:15             ` Rik van Riel
2002-09-03 21:54             ` Anton Altaparmakov
2002-09-03 22:46               ` Andreas Dilger
2002-09-03 23:19               ` Daniel Phillips
2002-09-04  0:18                 ` Anton Altaparmakov
2002-09-04  5:23                 ` David Lang
2002-09-04  7:16             ` Helge Hafting
2002-09-04  8:39               ` Andreas Dilger
2002-09-04 12:07                 ` Helge Hafting
2002-09-04 13:03                   ` Hans Reiser
2002-09-04  8:41               ` Peter T. Breuer
2002-09-04  7:50             ` Joachim Breuer [this message]
     [not found]               ` <3D75F8B0.8C7E974E@aitel.hist.no>
2002-09-04 21:26                 ` Joachim Breuer
2002-09-04  9:26             ` Lars Marowsky-Bree
2002-09-03 16:58     ` Anton Altaparmakov
2002-09-03 17:26       ` 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=m38z2i9os2.fsf@venus.fo.et.local \
    --to=jmbreuer@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ptb@it.uc3m.es \
    /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

Powered by JetHome