Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: David Nicol <davidnicol@gmail.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: the idea for improving the performance of b-tree search
Date: Wed, 13 Oct 2010 11:45:45 -0400	[thread overview]
Message-ID: <20101013154545.GW22691@think> (raw)
In-Reply-To: <AANLkTimC=HXPBMxcCL5dx0edN-Z+XzcHpe+G5Bi1hqoX@mail.gmail.com>

On Wed, Oct 13, 2010 at 10:22:30AM -0500, David Nicol wrote:
> On Wed, Oct 13, 2010 at 6:24 AM, Chris Mason <chris.mason@oracle.com>=
 wrote:
>=20
> > 3) Do delayed inode deletion. =A0See above, but change the word ins=
ert
> > with delete ;)
>=20
> And the reserved-for-the-future-but-not-used-yet flags field in the
> ioctl#21 control structure gets a use: bits to indicate for the
> completion of which of the potential delayed things the caller is
> waiting.

This is similar to the delayed allocation we already do for file data
extents.  It is supposed to be transparent to userland, and just a way
to more efficiently poke the on disk structures.

-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
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:[~2010-10-13 15:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-13  9:00 the idea for improving the performance of b-tree search Miao Xie
2010-10-13 11:24 ` Chris Mason
2010-10-13 15:22   ` David Nicol
2010-10-13 15:45     ` Chris Mason [this message]
2010-10-13 20:38       ` David Nicol
2010-10-18  2:41 ` Shaohua Li
2010-10-18  9:36   ` Miao Xie

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=20101013154545.GW22691@think \
    --to=chris.mason@oracle.com \
    --cc=davidnicol@gmail.com \
    --cc=linux-btrfs@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