linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Dan Williams <dan.j.williams@intel.com>
Cc: NeilBrown <neilb@suse.de>, linux-raid <linux-raid@vger.kernel.org>
Subject: Re: [mdadm git pull] platform support v2 and other fixes
Date: Thu, 18 Dec 2008 17:07:20 +1100	[thread overview]
Message-ID: <18761.59544.163344.177425@notabene.brown> (raw)
In-Reply-To: message from Dan Williams on Monday December 8

On Monday December 8, dan.j.williams@intel.com wrote:
> Hi Neil,
> 
> So here is a second attempt at platform support.  I asked around about
> scanning for the option-rom and the solution I settled on was to port
> the kernel's "Adapter ROM" detection code to userspace (probe_roms.c
> from arch/x86/kernel/probe_roms_32.c).  This at least makes mdadm bug
> compatible with the kernel, and avoids scanning the entire region
> indiscriminately.
> 
> Create support got two major fixes:
> 1/ calculating a common start offset by merging get_extents() results
> 2/ explicitly passing the target member disks in the metadata update
> message
> 
> Despite the platform support and these fixes I am still investigating
> whether mdadm can create configurations that the option-rom does not
> understand.  Stay tuned...
> 
> Lastly I added a regression test to stress the overlapping create case,
> it adds some infrastructure for tests to define their own environment.
> 
> As always, please have a look.

Thanks.
I confess I haven't read all of the details, but I've looked at the
"interesting" parts (for some value of 'interesting') and they seem to
make sense.
Pulled and pushed.

Thanks.
NeilBrown

      reply	other threads:[~2008-12-18  6:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-09  1:29 [mdadm git pull] platform support v2 and other fixes Dan Williams
2008-12-18  6:07 ` Neil Brown [this message]

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=18761.59544.163344.177425@notabene.brown \
    --to=neilb@suse.de \
    --cc=dan.j.williams@intel.com \
    --cc=linux-raid@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).