All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grigory Makarevich <grigorymakarevich@gmail.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs experimental branch updates
Date: Sun, 15 Mar 2009 15:13:15 -0400	[thread overview]
Message-ID: <49BD534B.7030303@gmail.com> (raw)
In-Reply-To: <1236959774.17095.3.camel@think.oraclecorp.com>

Dear All,

I was wondering if the experimental branch is smth. different or it is 
the same
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable-standalone.git

That repository does not seem to have any branches other than head and 
master.

Thank you,
Best regards,
Grigory Makarevich

Chris Mason wrote:
> Hello everyone,
>
> I've rebased the experimental branch to include most of the
> optimizations I've been working on.
>
> The two major changes are doing all extent tree operations in delayed
> processing queues and removing many of the blocking points with btree
> locks held.
>
> In addition to smoothing out IO performance, these changes really cut
> down on the amount of stack btrfs is using, which is especially
> important for kernels with 4k stacks enabled (fedora).
>
> -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
>   


  parent reply	other threads:[~2009-03-15 19:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-13 15:56 Btrfs experimental branch updates Chris Mason
2009-03-13 22:52 ` Steven Pratt
2009-03-14  1:33   ` Chris Mason
2009-03-15 14:38     ` Steven Pratt
2009-03-17  1:24       ` Chris Mason
2009-03-17 20:57         ` Steven Pratt
2009-03-18  1:18           ` Chris Mason
2009-03-15 19:13 ` Grigory Makarevich [this message]
2009-03-16 13:31   ` Chris Mason

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=49BD534B.7030303@gmail.com \
    --to=grigorymakarevich@gmail.com \
    --cc=chris.mason@oracle.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 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.