Skip to contentSkip to conversation

Efficient IPC mechanism on Linux

DISCUSSION Luca Veraldi 1 participant 1 message Sep 10, 2003 13 messages 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]

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

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

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

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

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

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

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

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

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

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

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

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

#13 lore raw
Quoted 2 lines

Can you forward-port your work to 2.6 kernel?
Can you benchmarkt it against the same primitives in 2.6 kernel?

I could do it only if there was an effective reason to do it. And there isn't.

They have just posted me a message with pipe latency under kernel 2.4. And it is exactly the same (apart some minor variations in misurements that are natural enough).

Quoted 2 lines

You have just started your work - are you going to finish it? Or it
was just-another-academical-study?

I consider my work finished.
I studied an efficient IPC mechanism and I tried to implement it on an existing Operating System.

I tried some other IPC primitives in benchmark tests and reported the comparisons between completion times.

I got my goal.

Quoted 5 lines

If you can try to develop new sematics for old syntax (shm* & etc) it
can be welcomed too.
And if it would be poll()able - it would be great. Applications which
do block on read()/getmsg() in real-life not that common, and as I've understood - this is the case for your message passing structure.

I'm not a kernel developer. Ask Linus Torvalds.

Bye,
Luca