Linux NFS development
 help / color / mirror / Atom feed
From: Tom Tucker <tom@opengridcomputing.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH  2/17] svcrdma: Fix race with dto_tasklet in svc_rdma_send
Date: Tue, 06 May 2008 19:45:08 -0500	[thread overview]
Message-ID: <C44665C4.4AFC2%tom@opengridcomputing.com> (raw)
In-Reply-To: <20080506211851.GM13484@fieldses.org>




On 5/6/08 4:18 PM, "J. Bruce Fields" <bfields@fieldses.org> wrote:

> On Mon, May 05, 2008 at 09:26:02PM -0500, Tom Tucker wrote:
>> 
>> 
>> 
>> On 5/5/08 5:06 PM, "J. Bruce Fields" <bfields@fieldses.org> wrote:
>> 
>>> On Fri, May 02, 2008 at 11:28:34AM -0500, Tom Tucker wrote:
>>>> The svc_rdma_send function will attempt to reap SQ WR to make room for
>>>> a new request if it finds the SQ full. This function races with the
>>>> dto_tasklet that also reaps SQ WR. To avoid calling the function
>>>> unnecessarily use test_and_clear_bit with the RDMAXPRT_SQ_PENDING
>>>> flag to serialize access to the sq_cq_reap function.
>>> 
>>> OK.  I won't pretend to understand much of this, but--would it be worth
>>> pulling out the added code here into a helper function, since it now
>>> exists in two different places?  (Especially if correctness depends on
>>> the same thing happening in both the places this bit can be cleared.)
>> 
>> Yes. Good suggestions.
>> 
>> BTW, this code is here because the SQ is undersized for big data. Since a
>> single NFS_READ/WRITE can result in an attempt to fetch a large amount of
>> data from the client (2M) and depending on certain HW resources this can
>> result in a lot of WR being posted to the SQ.
> 
> WR is write request, SQ is send queue?  (In which case this happens on
> nfs read operations?)  I'm behind....
> 
>> That said, there is a change coming in the 2.6.27 time frame that supports
>> what is called Fast NSMR register. This allows the transport to effectively
>> DMA map the entire transfer size (32k -- 2M) all as a single SGE. This will
>> take a lot of pressure off the SQ and effectively make this code
>> unnecessary.
> 
> OK!
> 
> Ideally we'd have patches for 2.6.27 in linux-next for a little while
> first, so we should try to have that ready in a month or so, when the
> -rc's start looking final.

It may be .28 then.  A lot of pieces have to come together...

> 
> --b.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



  reply	other threads:[~2008-05-07  0:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1209745721600-git-send-email-tom@opengridcomputing.com>
2008-05-02 22:37 ` [PATCH 0/17] svcrdma: RDMA transport driver close path cleanup J. Bruce Fields
2008-05-02 23:05   ` Tom Tucker
     [not found] ` <12097457211326-git-send-email-tom@opengridcomputing.com>
     [not found]   ` <1209745721248-git-send-email-tom@opengridcomputing.com>
     [not found]     ` <12097457213375-git-send-email-tom@opengridcomputing.com>
2008-05-05 19:31       ` [PATCH 1/17] svcrdma: Simplify receive buffer posting J. Bruce Fields
     [not found]       ` <12097457212336-git-send-email-tom@opengridcomputing.com>
     [not found]         ` <12097457212951-git-send-email-tom@opengridcomputing.com>
     [not found]           ` <12097457211122-git-send-email-tom@opengridcomputing.com>
     [not found]             ` <12097457223433-git-send-email-tom@opengridcomputing.com>
     [not found]               ` <12097457223971-git-send-email-tom@opengridcomputing.com>
     [not found]                 ` <12097457223635-git-send-email-tom@opengridcomputing.com>
     [not found]                   ` <12097457223351-git-send-email-tom@opengridcomputing.com>
2008-05-05 22:06                     ` [PATCH 2/17] svcrdma: Fix race with dto_tasklet in svc_rdma_send J. Bruce Fields
2008-05-06  2:26                       ` Tom Tucker
2008-05-06 21:18                         ` J. Bruce Fields
2008-05-07  0:45                           ` Tom Tucker [this message]
     [not found]                     ` <12097457221640-git-send-email-tom@opengridcomputing.com>
2008-05-05 22:08                       ` [PATCH 3/17] svcrdma: Fix return value " J. Bruce Fields
2008-05-06  2:03                         ` Tom Tucker
2008-05-06 21:08                           ` J. Bruce Fields
     [not found]                       ` <120974572253-git-send-email-tom@opengridcomputing.com>
     [not found]                         ` <12097457223519-git-send-email-tom@opengridcomputing.com>
     [not found]                           ` <12097457223927-git-send-email-tom@opengridcomputing.com>
     [not found]                             ` <12097457232986-git-send-email-tom@opengridcomputing.com>
2008-05-05 22:41                               ` [PATCH 7/17] svcrdma: Fix error handling during listening endpoint creation J. Bruce Fields
2008-05-06 14:48                                 ` Tom Tucker
2008-05-06 21:22                                   ` J. Bruce Fields
2008-05-07  0:48                                     ` Tom Tucker
2008-05-07  1:30                                       ` J. Bruce Fields
     [not found]                               ` <12097457231736-git-send-email-tom@opengridcomputing.com>
2008-05-05 22:52                                 ` [PATCH 8/17] svcrdma: Return error from rdma_read_xdr so caller knows to free context J. Bruce Fields
2008-05-06  2:05                                   ` Tom Tucker
2008-05-06 21:32     ` [PATCH 11/17] svcrdma: Use standard Linux lists for context cache J. Bruce Fields
2008-05-07  0:49       ` Tom Tucker
2008-05-06 21:46 ` [PATCH 0/17] svcrdma: RDMA transport driver close path cleanup J. Bruce Fields

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=C44665C4.4AFC2%tom@opengridcomputing.com \
    --to=tom@opengridcomputing.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    /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