* Re: system IPC
@ 2005-09-07 11:53 YH
2005-09-07 12:07 ` linux-os (Dick Johnson)
0 siblings, 1 reply; 3+ messages in thread
From: YH @ 2005-09-07 11:53 UTC (permalink / raw)
To: linux-kernel
It seems that the kernel disallows drivers to use system IPC.
Asynchronous communication mechanism is very effective mechanism among
various embedded OSes, even popular in RTOSes. Any reason why cannot use
sys_msgsnd and sys_msgrcv for kernel drivers?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: system IPC
2005-09-07 11:53 system IPC YH
@ 2005-09-07 12:07 ` linux-os (Dick Johnson)
2005-09-08 12:07 ` YH
0 siblings, 1 reply; 3+ messages in thread
From: linux-os (Dick Johnson) @ 2005-09-07 12:07 UTC (permalink / raw)
To: YH; +Cc: linux-kernel
On Wed, 7 Sep 2005, YH wrote:
> It seems that the kernel disallows drivers to use system IPC.
> Asynchronous communication mechanism is very effective mechanism among
> various embedded OSes, even popular in RTOSes. Any reason why cannot use
> sys_msgsnd and sys_msgrcv for kernel drivers?
>
Because they were not designed for use inside the kernel.
Cheers,
Dick Johnson
Penguin : Linux version 2.6.13 on an i686 machine (5589.54 BogoMips).
Warning : 98.36% of all statistics are fiction.
.
I apologize for the following. I tried to kill it with the above dot :
****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.
Thank you.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: system IPC
2005-09-07 12:07 ` linux-os (Dick Johnson)
@ 2005-09-08 12:07 ` YH
0 siblings, 0 replies; 3+ messages in thread
From: YH @ 2005-09-08 12:07 UTC (permalink / raw)
To: linux-os (Dick Johnson), linux-kernel
Are there any messaging mechanism (not signal) designed in kernel for
drivers to communicate user mode asynchronously? If not, any reason why
not using messaging in kernel as it is an effective and simple mechanism
for embedded and real time system?
Thank you.
Cheers.
Jim
linux-os (Dick Johnson) wrote:
> On Wed, 7 Sep 2005, YH wrote:
>
>
>>It seems that the kernel disallows drivers to use system IPC.
>>Asynchronous communication mechanism is very effective mechanism among
>>various embedded OSes, even popular in RTOSes. Any reason why cannot use
>>sys_msgsnd and sys_msgrcv for kernel drivers?
>>
>
>
> Because they were not designed for use inside the kernel.
>
> Cheers,
> Dick Johnson
> Penguin : Linux version 2.6.13 on an i686 machine (5589.54 BogoMips).
> Warning : 98.36% of all statistics are fiction.
> .
> I apologize for the following. I tried to kill it with the above dot :
>
> ****************************************************************
> The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.
>
> Thank you.
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-09-08 12:07 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-09-07 11:53 system IPC YH
2005-09-07 12:07 ` linux-os (Dick Johnson)
2005-09-08 12:07 ` YH
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox