All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-ext4@vger.kernel.org
Subject: Re: Space Maps?
Date: Mon, 24 Nov 2014 16:12:51 +0000 (UTC)	[thread overview]
Message-ID: <pan.2014.11.24.16.12.51@googlemail.com> (raw)
In-Reply-To: 547350F3.4050208@redhat.com

On Mon, 24 Nov 2014 09:38:27 -0600, Eric Sandeen wrote:

> On 11/24/14 9:33 AM, Theodore Ts'o wrote:
>> 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.
> 
> Was just checking that too. I'm always mystified by the folks who take the
> time to write & submit & present papers, but don't submit patches.

Thanks - that's all very sad. The author has a homepage at
http://saurabh.io/ so maybe someone with a sufficiently large army of
lawyers can contact him? I couldn't find any code right now either.

As for the patents - I'm outside the US and the paper explicitly mentions
using Linux' built-in RBTrees instead of AVL and a few othe minor
differences to ZFS, mostly relating to persisting the maps.

Holger

--
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

      reply	other threads:[~2014-11-24 16:13 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
2014-11-24 15:38   ` Eric Sandeen
2014-11-24 16:12     ` Holger Hoffstätte [this message]

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=pan.2014.11.24.16.12.51@googlemail.com \
    --to=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 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.