From: Theodore Ts'o <tytso@mit.edu>
To: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Space Maps?
Date: Mon, 24 Nov 2014 10:33:36 -0500 [thread overview]
Message-ID: <20141124153336.GA10992@thunk.org> (raw)
In-Reply-To: <pan.2014.11.24.12.43.51@googlemail.com>
On Mon, Nov 24, 2014 at 12:43:51PM +0000, Holger Hoffstätte wrote:
>
> Cleaning out some old research papers I came again across the proposal
> for "space maps" in ext4 [1]. What happened to that? Was it rejected
> due to too much risk or other technical reasons? The benefits sound
> appealing, so I was wondering if there's something fundamentally wrong
> with the suggested approach.
No one ever submitted patches. The other issue would be the 71 patents
which Jeff Bonwick claimed in his blog that Sun filed on technologies
relating ZFS. I wouldn't know whether there are any patents that read
on space maps, because like many companies (due to the United States'
dysfunctional patent system), my employer doesn't allow me to look at
patents --- and so I don't want to know (see previous comments about
the US's dysfunctional patent system). However, if anyone knows of
space maps being used in some file system before ZFS, that would
certainly be interesting and something that I _would_ want to know.
There is some thinking about using an in-memory AVL tree to track free
space, and demand-loading it from the bitmaps, but no one has had the
time to implement it to date.
Cheers,
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-11-24 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 12:43 Space Maps? Holger Hoffstätte
2014-11-24 15:33 ` Theodore Ts'o [this message]
2014-11-24 15:38 ` Eric Sandeen
2014-11-24 16:12 ` Holger Hoffstätte
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=20141124153336.GA10992@thunk.org \
--to=tytso@mit.edu \
--cc=holger.hoffstaette@googlemail.com \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).