public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Timothy Shimmin <tes@sgi.com>, xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [PATCH -mm] rescue large xfs preferred iosize from the inode diet patch
Date: Fri, 22 Sep 2006 16:19:50 +1000	[thread overview]
Message-ID: <20060922061950.GE3034@melbourne.sgi.com> (raw)
In-Reply-To: <45134DC5.4070607@sandeen.net>

On Thu, Sep 21, 2006 at 09:43:17PM -0500, Eric Sandeen wrote:
> Eric Sandeen wrote:
> >
> >Ah, ok, thanks guys.  Should have checked CVS I guess.
> >
> cc -= lkml;
> 
> actually the patch nathan put in seems like a lot of replicated code.

Yeah, that's what caught me - I looked at the tree which had nathan's
patch in it, and assumed that the stuff the -mm tree had cleaned it up
to use the generic_fillattr() code.

> But maybe he's solving some problem I didn't think of.

The difference is the old code updated the fields in the linux inode
with all the info from disk and then filled in the stat data from
the linux inode.  The new code gets the data from "disk" and puts it
straight into the the stat buffer without updating the linux inode.

> Any idea what?

I would have thought that we want what we report to userspace to be
consistent in the linux inode as well. I suppose that by duplicating
the code we removed a copy of the data but I see little advantage
from doing that considering the extra code to do it and the fat that
the linux inode may not be up to date now....

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  reply	other threads:[~2006-09-22  6:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-21 22:33 [PATCH -mm] rescue large xfs preferred iosize from the inode diet patch Eric Sandeen
2006-09-22  1:03 ` David Chinner
2006-09-22  2:03 ` Timothy Shimmin
2006-09-22  2:23   ` Eric Sandeen
2006-09-22  2:43     ` Eric Sandeen
2006-09-22  6:19       ` David Chinner [this message]
2006-09-22  7:50         ` Timothy Shimmin
2006-09-22 23:10   ` Andrew Morton
2006-09-22 23:19     ` Eric Sandeen
2006-09-22 23:34       ` Andrew Morton
2006-09-25  8:02     ` Timothy Shimmin

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=20060922061950.GE3034@melbourne.sgi.com \
    --to=dgc@sgi.com \
    --cc=sandeen@sandeen.net \
    --cc=tes@sgi.com \
    --cc=xfs@oss.sgi.com \
    /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