From: Joachim Breuer <jmbreuer@gmx.net>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] mount flag "direct" (fwd)
Date: Wed, 04 Sep 2002 23:26:08 +0200 [thread overview]
Message-ID: <m3heh5la4v.fsf@venus.fo.et.local> (raw)
In-Reply-To: <3D75F8B0.8C7E974E@aitel.hist.no> (Helge Hafting's message of "Wed, 04 Sep 2002 14:12:32 +0200")
Helge Hafting <helgehaf@aitel.hist.no> writes:
> Joachim Breuer wrote:
>> > 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
>>
> You can't just invalidate like that, you'll need synchronization.
> Something like "I want write access to this block - stop using it."
> And then you _wait_, until everybody else has released it. This
> could take some time if someone was busy using it.
More or less what I meant - I assumed the requirement of mutual
exclusion was already agreed upon. I might have phrased it more
clearly as in "the locking protocol provides the "other" nodes with
sensible invalidation data". Something which a "budgeting" type
locking protocol would not normally do (allow each node a range of its
own for exclusive writes; everyone can read everywhere (with a bit
more locking to make the writes look atomic if they aren't already
perhaps)).
>> 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).
>
> Possible only when there is a shared bus. Of course today's
> IDE/SCSI don't do this.
Well, SCSI can be *made* to do it (actually, this is what I had in
mind when I wrote it up) - but I don't know whether any mainstream
controllers would be able to "sniff" sensibly.
Anyway, 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"
next prev parent reply other threads:[~2002-09-04 21:21 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
[not found] ` <3D75F8B0.8C7E974E@aitel.hist.no>
2002-09-04 21:26 ` Joachim Breuer [this message]
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=m3heh5la4v.fsf@venus.fo.et.local \
--to=jmbreuer@gmx.net \
--cc=helgehaf@aitel.hist.no \
--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
Powered by JetHome