mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Harun Scheutzow <harun04@scheutzow.de>, linux-kernel@vger.kernel.org
Subject: Re: vfat file system extreme fragmentation on multiprocessor
Date: Thu, 11 Sep 2008 17:09:08 -0400	[thread overview]
Message-ID: <20080911210908.GC31271@csclub.uwaterloo.ca> (raw)
In-Reply-To: <48C97338.5080502@zytor.com>

On Thu, Sep 11, 2008 at 12:36:24PM -0700, H. Peter Anvin wrote:
> Lennart Sorensen wrote:
> >
> >I don't think fat filesystems have any concept of reserving space for
> >expanding files.  It's a pretty simple filesystem after all designed for
> >a single cpu machine with a non-multitasking OS (if you can call DOS an
> >OS).  Space tends to be allocated from the start of the disk wherever
> >free space is found since otherwise you would have to go searching for
> >the free space, which isn't that efficient.
> >
> 
> Well, you can always do that in-memory.

It still involves searching no matter where you do it.  With FAT-16 that
means up to 2^16 clusters to search through.  With FAT-32 even more.  It
doesn't have a cluster bitmap to speed things up.

-- 
Len Sorensen

  reply	other threads:[~2008-09-11 21:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-11 18:01 Harun Scheutzow
2008-09-11 19:10 ` Lennart Sorensen
2008-09-11 19:36   ` H. Peter Anvin
2008-09-11 21:09     ` Lennart Sorensen [this message]
2008-09-11 21:43       ` H. Peter Anvin
2008-09-11 20:11   ` Harun Scheutzow
2008-09-11 21:20     ` Lennart Sorensen
2008-09-11 23:03       ` Harun Scheutzow
2008-09-11 23:50 ` Andrew Morton
     [not found] <baZfg-1yC-3@gated-at.bofh.it>
     [not found] ` <baZS2-2rX-15@gated-at.bofh.it>
2008-09-12 13:19   ` Bodo Eggert
2008-09-12 22:11     ` Harun Scheutzow

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=20080911210908.GC31271@csclub.uwaterloo.ca \
    --to=lsorense@csclub.uwaterloo.ca \
    --cc=harun04@scheutzow.de \
    --cc=hpa@zytor.com \
    --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

all inboxes | Powered by JetHome®