linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernd Schubert <bschubert@ddn.com>
To: Andi Kleen <andi@halobates.de>
Cc: Bernd Schubert <bs_lists@aakef.fastmail.fm>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	Andreas Dilger <andreas.dilger@oracle.com>
Subject: Re: status of MMP?
Date: Fri, 7 May 2010 17:14:51 +0200	[thread overview]
Message-ID: <4BE42E6B.90405@ddn.com> (raw)
In-Reply-To: <87zl0b21ki.fsf@basil.nowhere.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/07/2010 05:06 PM, Andi Kleen wrote:
> Bernd Schubert <bs_lists@aakef.fastmail.fm> writes:
> 
>>
>> Lustres ldiskfs already has MMP support for several years and I would like to 
>> know what is the blocker for ext4? Updating the MMP patches for ext4-git 
>> should be fairly simple.
> 
> AFAIK simply nobody has done the work and submitted it.
> 
> Simply adding it would break LVM snapshots though, so there's a 
> compatibility issue.

Well, firstly, you are not forced to enable MMP. And then, I don't
understand what should be the issue with MMP. We use snapshots + ldiskfs
+ MMP all the time.


I have a basic understanding how the MMP code works, but not as thorough
as the Orcacle Lustre team. Andreas, would you mind if I post updated
patches here?

Cheers,
Bernd
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkvkLmsACgkQqh74FqyuOzT0bwCfQQRWqaUcTM0xQ1dgyAv483t1
2fQAniCT6AWBdqJiKWQmpUMdYvEKKubW
=U2NE
-----END PGP SIGNATURE-----

  reply	other threads:[~2010-05-07 15:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 21:30 status of MMP? Bernd Schubert
2010-05-07 15:06 ` Andi Kleen
2010-05-07 15:14   ` Bernd Schubert [this message]
2010-05-07 19:29     ` Andreas Dilger

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=4BE42E6B.90405@ddn.com \
    --to=bschubert@ddn.com \
    --cc=andi@halobates.de \
    --cc=andreas.dilger@oracle.com \
    --cc=bs_lists@aakef.fastmail.fm \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).