All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
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: Thu, 21 Sep 2006 21:43:17 -0500	[thread overview]
Message-ID: <45134DC5.4070607@sandeen.net> (raw)
In-Reply-To: <4513493F.8090005@sandeen.net>

Eric Sandeen wrote:
> Timothy Shimmin wrote:
> 
>> Looked at your patch and then at our xfs code in the tree and
>> the existing code is different than what yours is based on.
>> I then noticed in the logs Nathan has actually made changes for this:
>>
>> ----------------------------
>> revision 1.254
>> date: 2006/07/17 10:46:05;  author: nathans;  state: Exp;  lines: +20 -5
>> modid: xfs-linux-melb:xfs-kern:26565a
>> Update XFS for i_blksize removal from generic inode structure
>> ----------------------------
>> I even reviewed the change (and I don't remember it - getting old).
>>
>> I looked at the mods scheduled for 2.6.19 and this is one of them.
>>
>> So the fix for this is coming soon (and the fix is different from the
>> one above).
> 
> 
> Ah, ok, thanks guys.  Should have checked CVS I guess.
> 
> -Eric
> 

cc -= lkml;

actually the patch nathan put in seems like a lot of replicated code.

http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_iops.c.diff?r1=text&tr1=1.254&r2=text&tr2=1.253&f=h

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

Any idea what?

-Eric

  reply	other threads:[~2006-09-22  2:44 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 [this message]
2006-09-22  6:19       ` David Chinner
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=45134DC5.4070607@sandeen.net \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.