mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@arcor.de>
To: Anton Altaparmakov <aia21@cantab.net>
Cc: "Peter T. Breuer" <ptb@it.uc3m.es>,
	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 01:17:49 +0200	[thread overview]
Message-ID: <E17n5sj-0006CY-00@starship> (raw)
In-Reply-To: <5.1.0.14.2.20020905235933.04082dc0@pop.cus.cam.ac.uk>

On Friday 06 September 2002 01:06, Anton Altaparmakov wrote:
> At 23:45 05/09/02, Daniel Phillips wrote:
> >On Wednesday 04 September 2002 16:13, Anton Altaparmakov wrote:
> > > Did you read my post which you can lookup on the below url?
> > >
> > > http://marc.theaimsgroup.com/?l=linux-kernel&m=103109165717636&w=2
> > >
> > > That explains what a single byte write to an uncached ntfs volume entails.
> > > (I failed to mention there that you would actually need to read the block
> > > first modify the one byte and then write it back but if you write
> > > blocksize based chunks at once the RCW falls away.
> > > And as someone else pointed out I failed to mention that the entire
> > > operation would have to keep the entire fs locked.)
> > >
> > > If it still isn't clear let me know and I will attempt to explain again in
> > > simpler terms...
> >
> >Anton, it's clear he understands the concept, and doesn't care because
> >he does not intend his application to access the data a byte at a time.
> >
> >Your points are correct, just not relevant to what he wants to do.
> 
> Daniel,
> 
> The procedure described is _identical_ if you want to access 1TiB at a 
> time, because the request is broken down by the VFS into 512 byte size 
> units and I think I explained that, too. And for _each_ 512 byte sized unit 
> of those 1TiB you would have to repeat the _whole_ of the described 
> procedure.

Well, remember, he was going to use o_direct, so he can get away with pretty
crude locking.

> It is not clear to me he understands the concept at all. He thinks that you 
> need to read the disk inode just once and then you immediately read all the 
> 1TiB of data and somehow all this magic is done by the VFS. This is 
> complete crap and is _NOT_ how the Linux kernel works. The VFS breaks every 
> request into super block->s_blocksize sized units and _each_ and _every_ 
> request is _individually_ looked up as to where it is on disk.

He was going to go hack the vfs, so in his mind, practical issues of how the
vfs works now aren't an obstacle.  The only mistake he's making is seriously
underestimating how much effort is required to learn enough to do this kind
of surgery and have a remote chance that the patient will survive.

-- 
Daniel

  reply	other threads:[~2002-09-05 23:11 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 [this message]
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
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=E17n5sj-0006CY-00@starship \
    --to=phillips@arcor.de \
    --cc=aia21@cantab.net \
    --cc=david.lang@digitalinsight.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ptb@it.uc3m.es \
    --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®