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 11/15] knfsd: RDMA transport core
Date: Fri, 18 May 2007 14:36:28 -0500 [thread overview]
Message-ID: <1179516988.23385.171.camel@trinity.ogc.int> (raw)
In-Reply-To: <20070518192443.GD4843@fieldses.org>
On Fri, 2007-05-18 at 15:24 -0400, J. Bruce Fields wrote:
> On Fri, May 18, 2007 at 12:45:52PM -0500, Tom Tucker wrote:
> > + printk("svcrdma: new connection %p accepted with the following "
> > + "attributes:\n"
> > + "\tlocal_ip : %d.%d.%d.%d\n"
> > + "\tlocal_port : %d\n"
> > + "\tremote_ip : %d.%d.%d.%d\n"
> > + "\tremote_port : %d\n"
> > + "\tmax_sge : %d\n"
> > + "\tsq_depth : %d\n"
> > + "\tmax_requests : %d\n"
> > + "\tread throttle : %s\n"
> > + "\tord : %d\n",
> > + newxprt,
> > + NIPQUAD(((struct sockaddr_in*)&newxprt->sc_cm_id->
> > + route.addr.src_addr)->sin_addr.s_addr),
> > + ntohs(((struct sockaddr_in*)&newxprt->sc_cm_id->
> > + route.addr.src_addr)->sin_port),
> > + NIPQUAD(((struct sockaddr_in*)&newxprt->sc_cm_id->
> > + route.addr.dst_addr)->sin_addr.s_addr),
> > + ntohs(((struct sockaddr_in*)&newxprt->sc_cm_id->
> > + route.addr.dst_addr)->sin_port),
> > + newxprt->sc_max_sge,
> > + newxprt->sc_sq_depth,
> > + newxprt->sc_max_requests,
> > + (svcrdma_read_throttle?"TRUE":"FALSE"),
> > + newxprt->sc_ord);
>
> I assume these massive printk's are meant to be dprintk's (if they're
> meant to be left in at all).
It shows up once per mount. I thought it was useful, but perhaps not...
>
> > +/*
> > + * Setup the reply buffer for the svc_process function to write the
> > + * RPC into.
> > + */
> > +static int svc_rdma_prep_reply_buf(struct svc_rqst *rqstp)
> > +{
> > + struct kvec *resv = &rqstp->rq_res.head[0];
> > +
> > + /* setup response xdr_buf.
> > + * Initially it has just one page
> > + */
> > + rqstp->rq_resused = 1;
> > + resv->iov_base = page_address(rqstp->rq_respages[0]);
> > + resv->iov_len = 0;
> > + rqstp->rq_res.pages = rqstp->rq_respages+1;
> > + rqstp->rq_res.len = 0;
> > + rqstp->rq_res.page_base = 0;
> > + rqstp->rq_res.page_len = 0;
> > + rqstp->rq_res.buflen = PAGE_SIZE;
> > + rqstp->rq_res.tail[0].iov_base = NULL;
> > + rqstp->rq_res.tail[0].iov_len = 0;
> > +
> > + return 0;
> > +}
>
> I think this is a repeat of a question from yesterday--I'm not sure why
> we bothered to pull this out into separate function when the
> implementations all end up being identical, except for the one line for
> the record length in the tcp case?
>
Yeah, you're right. Maybe it shouldn't be prepare_buffer, but rather
"prepare_header". Then you'd keep the buffer code common and just have
the one line function for the TCP record len.
> > +
> > +/*
> > + * This request cannot be handled right now. Allocate a structure to
> > + * keep it's state pending completion processing. To accomplish this, the
> > + * function creates an svc_rdma_op_ctxt that looks like a receive completion and
> > + * enqueues it on the svc_sock's deferred request list. When*
> > + * svc_rdma_recvfrom is subsequently called, it first checks if there is a
> > + * deferred RPC and if there is:
> > + * - Takes the deferred request off the deferred request queue
> > + * - Extracts the svc_rdma_op_ctxt from the deferred request structure
> > + * - Frees the deferred request structure
> > + * - Skips the ib_cq_poll call and processes the svc_rdma_op_ctxt as if it had
> > + * just come out of an WR pulled from the CQ.
> > + */
> > +static struct cache_deferred_req *
> > +svc_rdma_defer(struct cache_req *req)
> > +{
> > + struct svc_rqst *rqstp = container_of(req, struct svc_rqst, rq_chandle);
> > + struct svcxprt_rdma *xprt;
> > + struct svc_rdma_deferred_req *dr;
> > +
> > + dprintk("svcrdma: deferring request on \n"
> > + " rqstp=%p\n"
> > + " rqstp->rq_arg.len=%d\n",
> > + rqstp,
> > + rqstp->rq_arg.len);
> > +
> > + /* if more than a page, give up FIXME */
> > + if (rqstp->rq_arg.page_len)
> > + return NULL;
> > + BUG_ON(rqstp->rq_deferred);
> > + xprt = (struct svcxprt_rdma*)rqstp->rq_sock;
> > + retry:
> > + dr = kmalloc(sizeof(struct svc_rdma_deferred_req), GFP_KERNEL);
> > + if (!dr) {
> > + printk(KERN_INFO "svcrdma: sleeping waiting for memory\n");
> > + schedule_timeout_uninterruptible(msecs_to_jiffies(1000));
> > + goto retry;
> > + }
>
> Why not return NULL, as svc_defer() does?
>
I think you're right. I'll fix this.
> --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
next prev parent reply other threads:[~2007-05-18 19:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 17:45 [RFC,PATCH 11/15] knfsd: RDMA transport core Tom Tucker
2007-05-18 19:07 ` Trond Myklebust
2007-05-18 20:07 ` Tom Tucker
2007-05-18 21:17 ` Trond Myklebust
2007-05-19 4:32 ` Tom Tucker
2007-05-21 7:16 ` Neil Brown
2007-05-21 16:02 ` Tom Tucker
2007-05-22 5:36 ` Neil Brown
2007-05-22 15:23 ` Tom Tucker
2007-05-18 19:24 ` J. Bruce Fields
2007-05-18 19:36 ` Tom Tucker [this message]
2007-05-18 19:42 ` J. Bruce Fields
2007-05-23 14:09 ` Greg Banks
2007-05-23 14:43 ` Tom Tucker
2007-05-23 14:55 ` Greg Banks
2007-05-23 15:03 ` Trond Myklebust
2007-05-23 15:12 ` Tom Tucker
2007-05-23 15:37 ` Trond Myklebust
2007-05-23 16:02 ` Tom Tucker
2007-05-23 16:35 ` Greg Banks
2007-05-23 16:29 ` Greg Banks
2007-05-23 18:07 ` Trond Myklebust
2007-05-23 18:19 ` Talpey, Thomas
2007-05-23 18:37 ` Trond Myklebust
2007-05-23 18:59 ` Talpey, Thomas
2007-05-23 20:01 ` Trond Myklebust
2007-05-23 21:00 ` Talpey, Thomas
2007-05-24 8:35 ` Greg Banks
2007-05-24 13:45 ` Talpey, Thomas
2007-05-23 15:03 ` Tom Tucker
2007-05-21 7:11 ` Neil Brown
2007-05-21 10:02 ` Greg Banks
2007-05-21 15:58 ` Tom Tucker
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=1179516988.23385.171.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox