From: Alex Tomas <bzzz@tmi.comex.ru>
To: Andrew Morton <akpm@digeo.com>
Cc: jlnance@unity.ncsu.edu, linux-kernel@vger.kernel.org
Subject: Re: 2.5.64-mm6
Date: 14 Mar 2003 23:10:20 +0300 [thread overview]
Message-ID: <m3y93haevn.fsf@lexa.home.net> (raw)
In-Reply-To: <20030314120537.715e5bf0.akpm@digeo.com>
>>>>> Andrew Morton (AM) writes:
AM> jlnance@unity.ncsu.edu wrote:
>>
>> Andrew, I am not sure what you mean by this. Are you saying that
>> the way ld accesses files causes the blocks on the disk to be
>> layed out poorly? That is the only thing I can think of that
>> would get fixed by copying.
>>
AM> Exactly that. ld seeks all over the file when adding new blocks
AM> to it, so with ext2 and ext3 (at least) there is poor
AM> correspondence between file offset and block indices.
hmm. I thought delayed allocation should solve this problem. Isn't it?
next prev parent reply other threads:[~2003-03-14 20:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 11:26 2.5.64-mm6 Andrew Morton
2003-03-13 16:23 ` 2.5.64-mm6 Jeremy Fitzhardinge
2003-03-13 19:34 ` 2.5.64-mm6 Andrew Morton
2003-03-14 3:04 ` 2.5.64-mm6 Steven Cole
2003-03-14 3:28 ` 2.5.64-mm6 Andrew Morton
2003-03-14 3:46 ` 2.5.64-mm6 Shawn
2003-03-14 3:51 ` 2.5.64-mm6 Andrew Morton
2003-03-14 3:56 ` 2.5.64-mm6 Robert Love
2003-03-14 13:31 ` 2.5.64-mm6 jlnance
2003-03-14 20:05 ` 2.5.64-mm6 Andrew Morton
2003-03-14 20:10 ` Alex Tomas [this message]
2003-03-14 20:22 ` 2.5.64-mm6 Andrew Morton
2003-03-14 20:19 ` 2.5.64-mm6 Alex Tomas
2003-03-13 20:35 ` 2.5.64-mm6 Thomas Molina
2003-03-14 9:29 ` 2.5.64-mm6 Alexander Hoogerhuis
2003-03-14 11:55 ` 2.5.64-mm6 Andrew Morton
2003-03-15 8:38 ` 2.5.64-mm6 Alexander Hoogerhuis
2003-03-14 12:01 ` 2.5.64-mm6 Helge Hafting
2003-03-14 12:14 ` 2.5.64-mm6 Andrew Morton
2003-03-14 20:38 ` 2.5.64-mm6 Eli Carter
2003-03-14 20:53 ` 2.5.64-mm6 Andrew Morton
2003-03-14 22:01 ` 2.5.64-mm6 Eli Carter
2003-03-14 22:21 ` 2.5.64-mm6 Andrew Morton
[not found] <20030313032615.7ca491d6.akpm@digeo.com.suse.lists.linux.kernel>
2003-03-13 13:36 ` 2.5.64-mm6 Andi Kleen
2003-03-13 19:32 ` 2.5.64-mm6 Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2003-03-13 13:42 2.5.64-mm6 Felipe Alfaro Solana
2003-03-13 21:49 2.5.64-mm6 Felipe Alfaro Solana
2003-03-14 0:23 ` 2.5.64-mm6 Thomas Molina
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=m3y93haevn.fsf@lexa.home.net \
--to=bzzz@tmi.comex.ru \
--cc=akpm@digeo.com \
--cc=jlnance@unity.ncsu.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox