Linux NFS development
 help / color / mirror / Atom feed
From: Greg Banks <gnb@sgi.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Thomas Talpey <Thomas.Talpey@netapp.com>,
	Linux NFS Mailing List <nfs@lists.sourceforge.net>,
	Greg Banks <gnb@sgi.com>,
	Peter Leckie <pleckie@melbourne.sgi.com>
Subject: Re: [RFC, PATCH 7/14] knfsd: export svc_sock_enqueue, svc_sock_received
Date: Thu, 17 May 2007 17:45:18 +1000	[thread overview]
Message-ID: <20070517074518.GF27247@sgi.com> (raw)
In-Reply-To: <20070516211703.GF18927@fieldses.org>

On Wed, May 16, 2007 at 05:17:03PM -0400, J. Bruce Fields wrote:
> On Thu, May 17, 2007 at 05:24:25AM +1000, Greg Banks wrote:
> > 
> > Export svc_sock_enqueue() and svc_sock_received() so they
> > can be used by sunrpc server transport implementations
> > (even future modular ones).
> 
> Have you thought about how you'll handle the reference counting in the
> modular case?

Yes, but only thought not experimented nor discussed.  I was planning
to add a new file to /proc/fs/nfsd roughly analagous to the ports and
versions files, where the init script could write a string to indicate
which transports are enabled or disabled.  Transports would be managed
in a global list of structures analagous to struct xprt_type in Chuck's
client patches.  Enabling from userspace would search this list, try
a module load on failure, and bump the refcount.  Disabling would
shut down all svc_sock belonging to the transport type, then drop
the module refcount.  Neither traffic from clients nor creation of
svc_socks would affect the module refcount.

Greg.
-- 
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
Apparently, I'm Bedevere.  Which MPHG character are you?
I don't speak for SGI.

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-05-17  7:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16 19:24 [RFC, PATCH 7/14] knfsd: export svc_sock_enqueue, svc_sock_received Greg Banks
2007-05-16 21:17 ` J. Bruce Fields
2007-05-17  7:45   ` Greg Banks [this message]
2007-05-17 12:23     ` Talpey, Thomas
2007-05-17 10:13 ` Neil Brown
2007-05-18  8:58   ` Greg Banks

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=20070517074518.GF27247@sgi.com \
    --to=gnb@sgi.com \
    --cc=Thomas.Talpey@netapp.com \
    --cc=bfields@fieldses.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=pleckie@melbourne.sgi.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