All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brad Johnson" <bradjohn263@comcast.net>
To: dm-devel <dm-devel@redhat.com>
Subject: Multipath selector policy additions
Date: Tue, 7 Feb 2006 16:10:19 -0600	[thread overview]
Message-ID: <00f901c62c33$48a82090$060aa8c0@workshop> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1048 bytes --]

I am a software developer that is new to this list. I understand that currently round-robin is the only implemented path selector type. I am scoping (for a major storage vendor) the effort required to implement additional selector types, as well as other work required to function properly with their hardware (possibly special device-specific hardware handlers, config file changes, etc.). I assume there is a procedure in place to allow developers to submit changes such as these to the public domain, and hope that eventually they may be included in some future distributions.

My questions are:

What is the procedure for submitting kernel patches for the device mapper?
Who (or what organization) owns responsibility for the device mapper kernel modules?
Who owns responsibility for the user-space multipath pieces?
Is anyone else currently developing additional path selector types?

I am sorry if my newbie questions are naive, but any help to point me in the right direction will be greatly appreciated.

Regards,
Brad Johnson

[-- Attachment #1.2: Type: text/html, Size: 1968 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



             reply	other threads:[~2006-02-07 22:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07 22:10 Brad Johnson [this message]
2006-02-09 19:37 ` Multipath selector policy additions Christophe Varoqui

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='00f901c62c33$48a82090$060aa8c0@workshop' \
    --to=bradjohn263@comcast.net \
    --cc=dm-devel@redhat.com \
    /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.