All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@tonian.com>
To: "Bhamare, Sachin" <sbhamare@panasas.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"osd-dev@open-osd.org" <osd-dev@open-osd.org>,
	"Harrosh, Boaz" <bharrosh@panasas.com>, Jim Rees <rees@umich.edu>,
	Steve Dickson <SteveD@redhat.com>
Subject: Re: [osd-dev] nfs-utils: userspace support for autologin feature in object layout driver
Date: Thu, 16 Feb 2012 17:58:30 +0200	[thread overview]
Message-ID: <4F3D27A6.4010200@tonian.com> (raw)
In-Reply-To: <CB5990C9.679A%sbhamare@panasas.com>

On 2012-02-10 01:02, Bhamare, Sachin wrote:
> Hi, 
>    I have been working on implementing autologin support for objectlayout
> driver in pNFS client. This feature would allow pNFS object clients to
> receive an URI (e.g. iscsi://<IP>:<PORT>) of a target OSD via
> GETDEVICEINFO rpc from the server. Object layout driver would then pass
> this information to an user space daemon which would perform the login
> task 
> depending on the protocol involved (e.g. Iscsi login using iscsiadm).
> 
> For userspace daemon, we have 2 implementation choices.
> 
> 1. Add new daemon (say, osdlogind) to nfs-utils which would process the
> upcalls from object layout driver via rpc_pipefs (very similar to the way
> blkmapd works)
> 2. Modify blkmapd in nfs-utils package to be able to process upcalls from
> the object layout driver and add new functionality to process these
> messages.
> 
> I think, (1) above is the simplest and cleanest way to go about
> implementing this. (2) adds an indirect dependency between block layout
> driver and object layout driver if they were to share the same rpc pipe to
> communicate with user space.

I'm inclined to agree but I'll defer this to Steve as the maintainer of nfs utils

Benny

> 
> Currently I have a simple implementation of 'osdlogind' coded up which
> borrows its design heavily from 'blkmapd' code. Please let me know what
> would be the preferred way to go about this. Thanks in advance for your
> inputs. 
> 
> Sachin Bhamare 
> Panasas Inc.
> 
> 
> _______________________________________________
> osd-dev mailing list
> osd-dev@open-osd.org
> http://mailman.open-osd.org/mailman/listinfo/osd-dev

      reply	other threads:[~2012-02-16 15:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09 23:02 nfs-utils: userspace support for autologin feature in object layout driver Bhamare, Sachin
2012-02-16 15:58 ` Benny Halevy [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=4F3D27A6.4010200@tonian.com \
    --to=bhalevy@tonian.com \
    --cc=SteveD@redhat.com \
    --cc=bharrosh@panasas.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=osd-dev@open-osd.org \
    --cc=rees@umich.edu \
    --cc=sbhamare@panasas.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.