From: Tom Tucker <tom@opengridcomputing.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Neil Brown <neilb@suse.de>, Tom Talpey <Thomas.Talpey@netapp.com>,
Linux NFS Mailing List <nfs@lists.sourceforge.net>,
Peter Leckie <pleckie@melbourne.sgi.com>,
Greg Banks <gnb@sgi.com>
Subject: Re: [RFC, PATCH 4/15] knfsd: map null socket to SOCK_STREAM in svc_max_payload
Date: Fri, 18 May 2007 13:50:30 -0500 [thread overview]
Message-ID: <1179514230.23385.145.camel@trinity.ogc.int> (raw)
In-Reply-To: <20070518184802.GC4843@fieldses.org>
On Fri, 2007-05-18 at 14:48 -0400, J. Bruce Fields wrote:
> On Fri, May 18, 2007 at 01:40:40PM -0500, Tom Tucker wrote:
> > Yes, however, we don't know what it's going to end up being yet and I'd
> > like to get this code reviewed, so I can work the issues in parallel.
>
> Sure.
>
> But I guess some questions will be easiest to answer when the two are
> completely integrated.
I also think by considering the two together, you can get a better
understanding of what's actually needed.
>
> > BTW, the current transport switch (before the mods) is up and running in
> > several locations.
>
> OK!
>
> --b.
-------------------------------------------------------------------------
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
prev parent reply other threads:[~2007-05-18 18:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 17:45 [RFC, PATCH 4/15] knfsd: map null socket to SOCK_STREAM in svc_max_payload Tom Tucker
2007-05-18 18:28 ` J. Bruce Fields
2007-05-18 18:40 ` Tom Tucker
2007-05-18 18:48 ` J. Bruce Fields
2007-05-18 18:50 ` Tom Tucker [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=1179514230.23385.145.camel@trinity.ogc.int \
--to=tom@opengridcomputing.com \
--cc=Thomas.Talpey@netapp.com \
--cc=bfields@fieldses.org \
--cc=gnb@sgi.com \
--cc=neilb@suse.de \
--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 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.