Re: Don't receive IRP_MJ_CREATE on a CreateFile


Welcome to one of the many reasons not to use shared memory. Instead of
shared memory use an IOCTL, to communicate, then you will recieve a cancel
for the IRP to be notified. Note: while it still has all the other
problems (besides process termination notification) you can use an IOCTL
to fake shared memory. The IOCTL is defined with METHOD_OUT_DIRECT and
the buffer passed in is "the shared memory region" you use to communicate.

Thanks for the answer and advices.


.

Relevant Pages

  • Re: openMosix Question
    ... Openmosix even has no programming interface. ... Processes with single threads. ... Processes that work with shared memory or use multiple threads can't ... The processes would have to communicate over the network. ...
    (comp.os.linux.development.apps)
  • Re: Dont receive IRP_MJ_CREATE on a CreateFile
    ... irps, the FS will. ... I can't rely on a "release" IOCTL because ... Welcome to one of the many reasons not to use shared memory. ... Don Burn (MVP, Windows DDK) ...
    (microsoft.public.development.device.drivers)
  • Re: kvm_read() vs ioctl performance
    ... overhead, assuming that the ioctl call is to a ... tried a shared memory page? ... same result with a stable API which is not libkvm... ...
    (freebsd-current)
  • Re: Needing info on passing data between applications. Win[C#]
    ... its been a long time when i used shared memory. ... this is also a very fas way to communicate. ... I am not a friend ...
    (microsoft.public.dotnet.languages.csharp)
  • Approaches of interprocess communication
    ... communicate via TCP/IP if the processes run on the same machine. ... CORBA -- similar to webservices but more complicated to code. ... Supposing both processes are written in Python, ... shared memory sound the most suited approach. ...
    (comp.lang.python)