Skip to contentSkip to conversation

socket API extensions workgroup at OpenGroup needs HELP

DISCUSSION Pete Zaitcev 5 participants 7 messages Feb 20, 2002 – Feb 21, 2002 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 7 lines

Interested people should contact the working group co-chairs for details about how to join the effort:
David Edmondson ([email protected]) or
Satya Sharma ([email protected])

The URL of the OpenGroup Interconnect Software Consortium is:
http://www.opengroup.org/icsc/

Yea, yea. The little problem here is that TOG is not getting it. When I see a website that says "Employees of member companies should send mail to the Consortium Administrator requesting access to the Member area.", I sure as hell is not getting a hardon about working on "overtaking Winsock" (and why exactly would we want to copy broken attempts to embrace and extend? Perhaps you should talk to a certain <i>monkey lover company</i> about it).

I would not mind to participate in something more open. If anyone has a suggestion of a mailing list which works in a way of tcp-implementors, but on the topic of socket API extensions for Infiniband, then I am interested.

-- Pete

#2 lore raw
Quoted 8 lines · Pete Zaitcev
Quoted 7 lines

Interested people should contact the working group co-chairs for details about how to join the effort:
David Edmondson ([email protected]) or
Satya Sharma ([email protected])

The URL of the OpenGroup Interconnect Software Consortium is:
http://www.opengroup.org/icsc/

Quoted 7 lines

Yea, yea. The little problem here is that TOG is not getting it. When I see a website that says "Employees of member companies should send mail to the Consortium Administrator requesting access to the Member area.", I sure as hell is not getting a hardon about working on "overtaking Winsock" (and why exactly would we want to copy broken attempts to embrace and extend? Perhaps you should talk to a certain <i>monkey lover company</i> about it).

Is that, by any chance, the same crowd that stands behind DAFS? If it _is_ the same crowd - send them to hell, they are beyond hope.

#3 lore raw
In reply to Pete Zaitcev
Quoted 4 lines

I would not mind to participate in something more open. If anyone has a suggestion of a mailing list which works in a way of tcp-implementors, but on the topic of socket API extensions for Infiniband, then I am interested.

You need to understand that most of the wacko DMA schemes have already been laughed out of the IETF - things like TCP RDMA have all turned into "this way happens to suit my hardware" "we'll we've got a patent on that way" and other debacles, followed by other people pointing out that they already get that performance without hacking up protocols and API's.

The existing socket API supports zero copy. SGI proved this a long time back (Im sure Larry McVoy can give dates). The existing unix aio and real time signal model supports all the notification needed for efficient scalable I/O.

You can also implement the entire socket layer in user space on top of hardware that already does all the brainwork (also been done).

In fact I have a submission for what is needed in API changes. Its a blank piece of paper right now.

I do agree and I ask the proposed chairs to comment on this - that the IETF should be involved and if there is such a working group it should be an IETF working group sponsored by the opengroup. That is where all the real experts are.

Alan
--
"The IETF already has more than enough RFCs that codify the obvious, make stupidity illegal, support truth, justice, and the IETF way, and generally demonstrate the author is a brilliant and valuable Contributor to The Standards Process." -- Vernon Schryver

#4 lore raw
In reply to Pete Zaitcev
Quoted 2 lines · Alexander Viro

Is that, by any chance, the same crowd that stands behind DAFS? If it _is_ the same crowd - send them to hell, they are beyond hope.

I almost thought that was directed at me, as Coda is kind of like a Distributed version of AFS.

phew, luckily DAFS it isn't related to AFS or Coda ;)

Jan

#5 lore raw
Quoted 8 lines · Jan Harkes
Quoted 2 lines · Alexander Viro

Is that, by any chance, the same crowd that stands behind DAFS? If it _is_ the same crowd - send them to hell, they are beyond hope.

I almost thought that was directed at me, as Coda is kind of like a Distributed version of AFS.

phew, luckily DAFS it isn't related to AFS or Coda ;)

DAFS isn't a filesystem - it's software equivalent of Freddy Kruger:
85 madmen^Wcompanies, one naive nurse^Widea, nightmares-inflicting monster conceived as the result of weeks of clusterfuck...

#6 lore raw
In reply to Jan Harkes
Quoted 8 lines · Alexander Viro
Quoted 4 lines · Jan Harkes
Quoted 2 lines · Alexander Viro

Is that, by any chance, the same crowd that stands behind DAFS? If it _is_ the same crowd - send them to hell, they are beyond hope.

Quoted 8 lines
Quoted 4 lines

I almost thought that was directed at me, as Coda is kind of like a Distributed version of AFS.

phew, luckily DAFS it isn't related to AFS or Coda ;)

DAFS isn't a filesystem - it's software equivalent of Freddy Kruger:
85 madmen^Wcompanies, one naive nurse^Widea, nightmares-inflicting monster conceived as the result of weeks of clusterfuck...

Yeah. No kidding. Anyone who thinks this is a good idea really hasn't thought about it clearly. It's nice marketing, sounds good, and is a crock. If you want this sort of thing, that's what kiobufs are for, and if kiobufs don't work right, that's a bug. Phooey on hacks.

Signature · 2 lines
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 
#7 lore raw
In reply to Pete Zaitcev
Quoted 2 lines

The existing socket API supports zero copy. SGI proved this a long time back (Im sure Larry McVoy can give dates).

Vernon was there long before I was and it worked long before I got there, all I did was hook up the networking plumbing to the file system plumbing so that you could move data without copying it.

Signature · 2 lines
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm