From: Andrew Morton <akpm@osdl.org>
To: bzzz@tmi.comex.ru
Cc: linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net
Subject: Re: [PATCH] minor optimization for EXT3
Date: Thu, 10 Jul 2003 08:51:55 -0700 [thread overview]
Message-ID: <20030710085155.40c78883.akpm@osdl.org> (raw)
In-Reply-To: <87isqaiegy.fsf@gw.home.net>
bzzz@tmi.comex.ru wrote:
>
> >>>>> Andrew Morton (AM) writes:
>
> AM> Alex Tomas <bzzz@tmi.comex.ru> wrote:
> >>
> >> Andreas Dilger proposed do not read inode's block during inode updating
> >> if we have enough data to fill that block. here is the patch.
>
> AM> ok, thanks. Could you please redo it for the current kernel?
>
> hmmm. it was against 2.5.72. I just tried it on 2.5.74 and all is OK.
>
2.5.74 is some crufty ancient old thing.
ext3_read_inode() got reorganised. Your latest patch will not apply to
current kernels.
The diff for the current devel kernel is always available at
http://www.kernel.org/pub/linux/kernel/v2.5/testing/cset/
The "gzipped full patch". You should use that when generating and testing
changess.
There is even a nice patch-script for it:
linus-patch http://www.kernel.org/pub/linux/kernel/v2.5/testing/cset/cset-20030710_0516.txt.gz
next prev parent reply other threads:[~2003-07-10 15:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 14:49 [PATCH] minor optimization for EXT3 Alex Tomas
2003-07-10 11:20 ` Andrew Morton
2003-07-10 15:33 ` bzzz
2003-07-10 15:51 ` Andrew Morton [this message]
2003-07-10 20:46 ` Alex Tomas
2003-07-10 17:01 ` Andrew Morton
2003-07-10 21:09 ` Alex Tomas
2003-07-10 19:14 ` Andreas Dilger
2003-07-10 15:56 ` Alex Tomas
[not found] <87smpeigio.fsf@gw.home.net.suse.lists.linux.kernel>
[not found] ` <20030710042016.1b12113b.akpm@osdl.org.suse.lists.linux.kernel>
[not found] ` <87y8z6gyt3.fsf@gw.home.net.suse.lists.linux.kernel>
2003-07-10 12:43 ` Andi Kleen
2003-07-10 16:51 ` Alex Tomas
2003-07-10 12:55 ` Andi Kleen
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=20030710085155.40c78883.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bzzz@tmi.comex.ru \
--cc=ext2-devel@lists.sourceforge.net \
--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 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.