During this week's conference call I reviewed the earlier work on Supporting Services regarding the semantics of an IA Address. Basically, because an IA...
Below are the changes for the format of the static registry as agreed at Wednesday call. Please, let me know if language is OK with you by the end today. ...
This posting is the first in a series covering issues about mapping the RDMAC iWARP verbs to DAT. This one deals with the handling of STags. The iWARP...
... Correction: digging deeper in the document, STags derived from Memory Regions (LMRs) are a distinct type from those derived from Memory Windows (RMRs). ...
The RDMAC iWARP verbs follow a very different model of kernel/user/hardware interactions than the IB verbs did. It is actually a major improvement. It allows...
... This is a bit of a nit, but by definition, all verbs talk to the RI. The RNIC itself is only accessed by vendor software that, with the RNIC, comprise the...
... I believe the answer to this question is that though the RI and verbs consumers may have to distinguish between the two types of STag, the actual verbs do...
... That's how I read the spec on the first pass, especially since identical control structures can be used to manage both LMRs and RMRs. But 8.1.3.2...
... The key point is that the software between the non-privileged Consumer and the RNIC, for purposes of the enumerated non-privileged operations, is presumed...
... DAT requires that the overflow be reported, but makes no requirements about what state an Event Stream (i.e., the CQ) is in after it has overflowed. There...
The InfiniBand verbs were also intended to allow posting directly to the hardware and to poll hardware for completions directly, without intervention of a...
... The user mode bottleneck I was referring to are the completion handlers. While a kDAPL upcall routine is carefully specified so as to be callable from...
I have thought about developing a DAT conformance test and would like to make the following proposal. Attached to this email is the simple prototype described...
Sears, Steven
sjs@...
May 6, 2003 1:29 pm
2321
Hello, This email message is a notification to let you know that a file has been uploaded to the Files area of the dat-discussions group. File :...
dat-discussions@yahoo...
May 6, 2003 6:56 pm
2322
This is the ratified uDAPL-1.1 spec still in color mode. I am waiting for the final tech writer feedback and then post the ratified version on DAT web site. ...
As requested in the conference call today, here is a description and list of objections to the current practice of the DAPL Reference Implementation (RI). Just...
Sears, Steven
sjs@...
May 7, 2003 5:50 pm
2326
An additional objection is that this method does not help when the remote server side is not using DAPL, nor when a non-DAPL client tries to connect to a DAPL...
Wittle, Mark
Mark.Wittle@...
May 7, 2003 6:19 pm
2327
Hello, This email message is a notification to let you know that a file has been uploaded to the Files area of the dat-discussions group. File :...
dat-discussions@yahoo...
May 8, 2003 10:21 pm
2328
Hello, This email message is a notification to let you know that a file has been uploaded to the Files area of the dat-discussions group. File :...
dat-discussions@yahoo...
May 8, 2003 10:23 pm
2329
Hello, This email message is a notification to let you know that a file has been uploaded to the Files area of the dat-discussions group. File :...
dat-discussions@yahoo...
May 8, 2003 10:25 pm
2330
Hello, This email message is a notification to let you know that a file has been uploaded to the Files area of the dat-discussions group. File :...
dat-discussions@yahoo...
May 8, 2003 10:29 pm
2331
In section 8.4.6 "Other static registry format", there are provisions for other platforms to specify their static registry format when their ref. impl. is...
Sherman Pun
sherman.pun@...
May 9, 2003 12:32 am
2332
... I have also a couple of questions regarding the static registry format. The spec states that the each entry starts with the IA name, but when that provider...
Sherman, 8.4.5 defined the static registry format for all Unixes and Windows. This includes all Unixes: linux, solaris, aix, bsd, hp-ux and others. 8.4.6 is...
Steffen, IA_Name is what Consumer gets from dat_registry_list_providers that extract information from the static Registry. This call need to list all available...
... In fact, I'd venture that 8.4.5 is appropriate for *any* OS that supports standard IO and has a local file system suitable for holding configuration files....
If 8.4.6 is confusing may be in the next version of the spec let remove it. This will keep only a single Static registry format! Arkady Arkady Kanevsky...
Having problems with message search?
Fill out this form to ensure your group is one of the first to be migrated to the new message search system.
