Alexander Viro wrote:
> On Thu, 10 Aug 2000, Daniel Phillips wrote:
>
> > Correct me if I'm wrong, but I think that if writepage ever needs to unmerge at
> > tail then it's an error. The tail should have already been unmerged by the
> > ext2_file_write,
it's ok with you to cc back to the list... It's called 'trolling for
more feedback'. I'm also trying to be a little bit didactic about the design
process for the benefit of list lurkers. :-)
> On 8/9/00, 4:55:13 PM, Daniel Phillips <[EMAIL PROTECTED]>
> >
n. Pretty big "but". I guess I know
what the next two installments in the Documenting series will be about.
D: Daniel Phillips
A: Alexander Viro
S: Stephen Tweedie
D> Stephen asked me some sharp questions about how this would work,
D> and after I answered them to his satisfaction
Hans Reiser wrote:
> Post your document on the reiserfs mailing list when you finish it,
> the ReiserFS team will enjoy reading it.
OK, and I hope your team will review it and post corrections - I'm
hoping somebody picks this up on the documentation lists and makes a
tutorial out of it, so it sho
Dave Cecil wrote:
>
> Daniel,
>
> >Here's the proposed mount-time tailmerging algorithm which was originally
> >posted as an attachment summarizing a series of emails between me and Stephen
> >Tweedie on this subject:
> >---
>
> [snip]
>
> first of all I admit to on
On Tue, 01 Aug 2000, Chris Mason wrote:
> On 8/1/00, 2:45:11 PM, Daniel Phillips <[EMAIL PROTECTED]>
> > writing past tail?
> > if so, unmerge tail block
> > generic file write
>
> > additions to write full page:
> > (within the per-bu
On Tue, 01 Aug 2000, Andreas Dilger wrote:
> You never mention what happens when a file doesn't have a tail yet,
> but then gets one...
Every file has a tail, unless it is exactly some number of blocks long. The
tail is the part at the end that doesn't fill a block completely. In my
terminolo
It should have read:
additions to read full page:
(within the per-buffer read)
is the file tailmerged?
if so, does this part map the tail block?
if so, get the tail block and copy the tail to the page
additions to write full page:
(within the per-buffer write)
is the fi
Chris Mason wrote:
> For reading the tail, take a look at how these functions interact:
>
> get_block
> generic_file_read
> block_read_full_page (ext2's readpage func)
>
> Putting the tail knowledge into ext2_file_read won't be enough, it won't
> cover mmaps. You have to make sure your readpage
Chris Mason wrote:
>
> On 7/30/00, 7:14:16 AM, Daniel Phillips
> <[EMAIL PROTECTED]> wrote regarding Re: Questions about
> the buffer+page cache in 2.4.0:
>
> > After digging a little deeper I can see that using the read actor
> > won't work because the
"Bill Rugolsky Jr." wrote:
> In an effort to document some of the changes that have gone into 2.4
> (particularly the VFS/MM changes), I'd like to mirror the entire
> linux-fsdevel, linux-mm, and linux-kernel archives going back at least
> to the start of 2.3.x.
Speaking of documenting, I saw rec
Daniel Phillips wrote:
> There are two obvious ways to do filesystem-specific special handling of the
> tail block: (1) in the 'read actor' that does the actual copy-to-user (see? yet
> another problem solved by an extra level of indirection!) or (2) in the
> inode->i
Daniel Phillips wrote:
> So now it's time to start asking questions.
I've been partway through lxr'ing the 2.4.0 VFS now, and all I can say is wow!
This really is a big improvement over 2.2.
Please treat all of the rest of this post as speculation: I'm not sure ho
Alexander Viro wrote:
>
> On Wed, 26 Jul 2000, Stephen C. Tweedie wrote:
>
> > For tail writes, I'd imagine we would just end up using the page cache
> > as a virtual cache as NFS uses it, and doing plain copy into the
> > buffer cache pages.
>
> Ouch. I _really_ don't like it - we end up with
After spending *far* too long getting lxr installed and working, I finally have
my favorite source browser working in the same place I email from :-) Meaning
that the next time I get hit with a tough question I'll be able to respond
having to go home and browsing the source first.
BTW, lxr is a
Alexander Viro wrote:
> On Wed, 26 Jul 2000, Stephen C. Tweedie wrote:
> > On Wed, Jul 26, 2000 at 03:19:46PM -0400, Alexander Viro wrote:
> >
> > > Erm? Consider that: huge lseek() + write past the end of file. Woops - got
> > > to unmerge the tail (it's an internal block now) and we've got no
>
On Wed, 26 Jul 2000, Alexander Viro wrote:
> On Wed, 26 Jul 2000, Daniel Phillips wrote:
>
> > Stephen asked me some sharp questions about how this would work,
> > and after I answered them to his satisfaction he asked me if I
> > would have time to implement this featur
think
implementing it will be very hard. All these things taken
together suggest that this is a good idea to try.
I have collected all the emails between me and Stephen and attached
them as an html document.
--
Daniel
Subject: Re: Tux2 filesystemDate: Fri, 14 Jul 2000 15:07:17 +0200
18 matches
Mail list logo
