From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Paul Clements <paul.clements@us.sios.com>
Cc: Andrey Utkin <andrey.krieger.utkin@gmail.com>,
kernel list <linux-kernel@vger.kernel.org>,
"nbd-general@lists.sourceforge.net"
<nbd-general@lists.sourceforge.net>
Subject: Re: NBD Maintainer
Date: Wed, 14 Jan 2015 22:14:58 +0530 [thread overview]
Message-ID: <20150114164458.GA2152@fool> (raw)
In-Reply-To: <CAECXXi4mEV2=-w95LJCDA=zf6f8_SCRBHYkp2tTwUuAJiOjaQQ@mail.gmail.com>
On Tue, Jan 13, 2015 at 02:26:01PM -0500, Paul Clements wrote:
> On Tue, Jan 13, 2015 at 11:14 AM, Andrey Utkin
> <andrey.krieger.utkin@gmail.com> wrote:
> > Hi Paul,
> > could you please describe
>
> > - how wide is NBD usage today (any estimation is ok),
>
> It depends somewhat on who you consider to be users. There are two
> groups of NBD "users":
>
> 1) integrators and admins (who work directly with nbd)
> 2) users of the systems and software that the first group creates
Hi Paul,
studied the driver code. looks like the driver is simple and the main work is being done by the nbd-client and nbd-server.
i was thinking of putting in my name for consideration, but being a newbie in lkml (have worked with drivers and server-client codes in my dayjob)
and seeing the vast user base i am not sure anymore. But will like to try if you are there for guidance.
sudip
>
> My guess is that the first group is in the hundreds. The second in the
> thousands. NBD usage tends to fall into one the following classes:
>
next prev parent reply other threads:[~2015-01-14 16:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 14:45 NBD Maintainer Paul Clements
2015-01-13 16:14 ` Andrey Utkin
2015-01-13 19:26 ` Paul Clements
2015-01-14 7:33 ` [Nbd] " Tuomas Räsänen
2015-01-14 8:37 ` Juan Antonio Martinez
2015-01-29 23:45 ` Wouter Verhelst
2015-01-14 9:11 ` Ming Lei
2015-01-14 16:44 ` Sudip Mukherjee [this message]
2015-01-14 17:02 ` Andrey Utkin
2015-01-14 17:10 ` Andrey Utkin
2015-01-14 18:08 ` Markus Pargmann
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=20150114164458.GA2152@fool \
--to=sudipm.mukherjee@gmail.com \
--cc=andrey.krieger.utkin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd-general@lists.sourceforge.net \
--cc=paul.clements@us.sios.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox