|
Back
Midas
Rome
Roody
Rootana
|
Midas DAQ System |
Not logged in |
|
|
14 Jul 2004, Piotr Zolnierczuk, , future direction discussion?
|
14 Jul 2004, Piotr Zolnierczuk, , future directions discussion?
|
14 Jul 2004, Stefan Ritt, , future direction discussion?
|
15 Jul 2004, Konstantin Olchanski, , future direction discussion?
|
|
Message ID: 23
Entry time: 14 Jul 2004
Reply to this: 24
25
|
Author: |
Piotr Zolnierczuk |
Topic: |
|
Subject: |
future direction discussion? |
|
|
Hi,
I think that rather than spending too much time on where to
put files and how to define the environment - I am guilty of that myself.
We should be perhaps have some discussion on the future of MIDAS.
Are we ready for 2.0?
Stefan - do you have any ideas/enhancements?
1) For one I would like to explore memory mapping (mmap()) on Linux
- I've used it once upon a time on DEC OSF/1 and I found it really
nice compared to shared memory.
From a user standpoint it behaves as a shared memory but is mapped
to a real file that can be easily "removed" when neccessary.
One really annoying thing in MIDAS is when it goes ballistic
the cleanup which is somewhat tricky.
The question if there is any performance penalty associated
2) Expanding hardware support:
a) custom microcontrolers?
b) more hardware
c) how about a "standard" Linux device /dev/midas
for various PCI cards (PCI<->CAMAC) (PCI<->VME)
3) I have never really seen a midas deployment that uses interrupts.
I do understand the ease of polling and the fact that these days
CPU's are cheap but sometimes it is important to use interrupts.
Any examples/experience?
?)
Piotr |