public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Wise <swise@opengridcomputing.com>
To: "Tung, Chien Tin" <chien.tin.tung@intel.com>
Cc: Andrea Gozzelino <Andrea.Gozzelino@lnl.infn.it>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"rolandd@cisco.com" <rolandd@cisco.com>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"pavel@ucw.cz" <pavel@ucw.cz>, "mingo@elte.hu" <mingo@elte.hu>,
	Eric B Munson <ebmunson@us.ibm.com>
Subject: Re: Socket Direct Protocol: help (2)
Date: Tue, 13 Apr 2010 15:20:58 -0500	[thread overview]
Message-ID: <4BC4D22A.6020700@opengridcomputing.com> (raw)
In-Reply-To: <2EFBCAEF10980645BBCFB605689E08E9047C7405A0@azsmsx506.amr.corp.intel.com>

Tung, Chien Tin wrote:
>>> NE020 supports 4 SGEs.  I don't know enough about SDP to know why it is
>>> using this calculation for # of send_sge:
>>>
>>> #define SDP_MAX_RECV_SKB_FRAGS (PAGE_SIZE > 0x8000 ? 1 : 0x8000 / PAGE_SIZE)
>>>
>>>
>>>       
>> Chien, does the NE020 support FMRs?  I looked at the nes ofed-1.5 code
>> and it appears to do nothing in the map_phys_fmr functions.
>>     
>
> We never implemented map_phys_fmr.  Is it relevant to the # of SGEs?
>   
No, but SDP uses FMRs.  I don't think it will run without FMR support.



  reply	other threads:[~2010-04-13 20:19 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <13381_1271060138_o3C8FUH8013968_2977669.1271060085255.SLOX.WebMail.wwwrun@imap.lnl.infn.it>
2010-04-12 14:33 ` Socket Direct Protocol: help (2) Andrea Gozzelino
2010-04-13 16:28   ` Tung, Chien Tin
2010-04-13 16:39     ` Steve Wise
2010-04-13 20:02       ` Tung, Chien Tin
2010-04-13 20:20         ` Steve Wise [this message]
2010-04-13 20:22           ` Tung, Chien Tin
2010-04-14  8:51             ` Andrea Gozzelino
2010-04-14 14:31               ` Amir Vadai
2010-04-14 14:46                 ` Amir Vadai
2010-04-14 15:01                   ` Tung, Chien Tin
2010-04-14 15:05                     ` Steve Wise
2010-04-14 15:14                       ` Andrea Gozzelino
2010-04-14 18:48                       ` Tung, Chien Tin
2010-04-15  6:24                         ` Amir Vadai
2010-04-15  7:07                           ` Andrea Gozzelino
2010-04-15  8:38                             ` Amir Vadai
2010-04-20 13:53                               ` Andrea Gozzelino
2010-04-21 12:01                                 ` Amir Vadai
2010-04-23 14:34                                   ` SDP bugs 2027 and 2028 Andrea Gozzelino
2010-04-25  7:35                                     ` Amir Vadai
2010-04-23 14:35                                   ` Andrea Gozzelino
2010-04-23 14:35                                   ` Socket Direct Protocol: help (2) Andrea Gozzelino
2010-04-14 14:54                 ` Steve Wise
2010-04-14 15:03                   ` Amir Vadai
2010-04-14 15:08                     ` Steve Wise
2010-04-14 15:16                       ` Amir Vadai
2010-04-14 19:24               ` Tung, Chien Tin

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=4BC4D22A.6020700@opengridcomputing.com \
    --to=swise@opengridcomputing.com \
    --cc=Andrea.Gozzelino@lnl.infn.it \
    --cc=chien.tin.tung@intel.com \
    --cc=ebmunson@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pavel@ucw.cz \
    --cc=peterz@infradead.org \
    --cc=rolandd@cisco.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