From: Kent Overstreet <kent.overstreet-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Mark Hills <mark-UrrBsZIrrsb10XsdtD+oqA@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: First observations with bcache
Date: Wed, 21 Sep 2011 23:13:39 -0700 [thread overview]
Message-ID: <20110922061339.GA14669@moria> (raw)
In-Reply-To: <1109101110320.2733-4jfXtw+jRJ582hYKe6nXyg@public.gmane.org>
Ok, I should have all the issues you found fixed. They're only compile
tested but they should be correct - tomorrow I'll pull them into the dev
branch and test them.
But I got that and the most recent stable code pushed to the public
repository. I got rid of the 2.6.34 branch, the bcache branch is now
based off 3.1.
You got it up and running? How's it working?
On Sat, Sep 10, 2011 at 02:44:56PM +0100, Mark Hills wrote:
> I took some time to try out bcache, on an x86 Dell PC with OCZ Agility 3
> SSD.
>
> The good news is that once I had applied various workarounds, thing seems
> to work as expected, both with 2.6.34 and with an updated 3.1 branch.
>
> I had to make a few modifications to get going, and then more to enable
> the various debug options.
>
> The most awkward problems seem to be the result of 32-bit architecture,
> and I think are highlighted by building as a module.
>
> I'll follow-up this email with the patches (based on bcache-3.1 branch),
> though I don't consider them to be long-term solutions; they show the
> changes I made.
>
> I some cases I've proposed a better solution, but thought I'd raise them
> here for discussion first.
>
> --
> Mark
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-09-22 6:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-10 13:44 First observations with bcache Mark Hills
[not found] ` <1109101110320.2733-4jfXtw+jRJ582hYKe6nXyg@public.gmane.org>
2011-09-10 13:45 ` [PATCH 1/7] Use exported call to up/down read Mark Hills
[not found] ` <1315662339-3115-1-git-send-email-mark-UrrBsZIrrsb10XsdtD+oqA@public.gmane.org>
2011-09-10 13:45 ` [PATCH 2/7] Provide 64-bit arithmetic functions Mark Hills
2011-09-10 13:45 ` [PATCH 3/7] Break fuzz test to allow building as module Mark Hills
2011-09-10 13:45 ` [PATCH 4/7] Don't require linkage against closure_lock Mark Hills
2011-09-10 13:45 ` [PATCH 5/7] Allow closure debugging without CONFIG_DEBUG_FS Mark Hills
2011-09-10 13:45 ` [PATCH 6/7] Temporary fix to pr_latency() Mark Hills
2011-09-10 13:45 ` [PATCH 7/7] Don't require latency_warn_ms from bcache_util.o Mark Hills
2011-09-10 21:39 ` [PATCH 1/7] Use exported call to up/down read Kent Overstreet
2011-09-22 6:13 ` Kent Overstreet [this message]
2011-09-22 23:14 ` First observations with bcache Mark Hills
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=20110922061339.GA14669@moria \
--to=kent.overstreet-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark-UrrBsZIrrsb10XsdtD+oqA@public.gmane.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