[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [dm-devel] Another cache target



On Thu, Dec 13 2012 at  9:19pm -0500,
Mike Snitzer <snitzer redhat com> wrote:

> On Thu, Dec 13 2012 at  8:16pm -0500,
> Darrick J. Wong <darrick wong oracle com> wrote:
> 
> > On Thu, Dec 13, 2012 at 04:57:15PM -0500, Mike Snitzer wrote:
> > > 
> > > agk's patches are here:
> > > http://people.redhat.com/agk/patches/linux/editing/series.html
> > > 
> > > But agk hasn't staged all the required patches yet.  I've imported agk's
> > > editing tree (and a couple other required patches that I previously
> > > posted to dm-devel, which aren't yet in agk's tree) into the
> > > 'dm-for-3.8' branch on my github tree here:
> > > git://github.com/snitm/linux.git
> > > 
> > > This 8 patch patchset from Joe should apply cleanly ontop of my
> > > 'dm-for-3.8' branch.
> > > 
> > > But if all you care about is a tree with all the changes then please
> > > just use Joe's github 'thin-dev' branch.
> > 
> > A full list of broken-out patches would've been nice, but oh well, I ate this
> > git tree. :)
> > 
> > Curiously, the Documentation/device-mapper/dm-cache.txt says to specify devices
> > in the order: metadata, origin, and cache, but the code (and Joe's mail) seeem
> > to want metadata, cache, origin.  This sort of makes me wonder what's going on?
> 
> The patch Joe posted has the proper order (metadata, cache, origin -- I
> fixed the ordering in dm-cache,txt and Joe pulled it in before posting
> the patches).  Seems Joe forgot to push his last few tweaks to his
> thin-dev branch.
> 
> > Also, I found a bug when using the mru policy.  If I do this:
> 
> Pretty sure you'd be best served to focus on the code Joe posted.  Maybe
> best to clone my github tree and start with my 'dm-for-3.8' branch.  And
> then apply all the patches Joe posted.

Also, AFAIK Joe pulled Linus latest tree from this afternoon into his
thin-dev; which included a bunch of bleeding v3.8 merge changes.
That makes his thin-dev inappropriate for stable testing.  You could
eaisly be hitting some early v3.8 issue.

My "dm-for-3.8" is v3.7 + the bulk of the DM patches destined for v3.8.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]