[Index] [Back] [Next]
Server space:
Server space is another ring upper the ikernel.
Server space contain a standart dynamic libruary for the all servers
that provide all works with ikernel, such as intercommunicating and
registration/removing functions calls.
Each of the server working in one security ring that strongly
separated with ikernel and user spaces for the stable and security
reasons. It has a weak point - this architecture doesn't works on the
CPU without MMU(stands for Memory Management Unit) and CPU that
doesn't supports more than two spaces rings.
Communications beetween the servers following via JP protocol, there
are two ways - via the ikernel security system or directly - it's
depends on the IPC routing rules that getting dynamically.
For external nodes there is an another way of communication - directly
by the intercommunicating with another node security system. It's take
a scalability and transparency and we're don't need in the non-trivial
networked filesystem implementation i.e. we're don't need for the
special networked filesystem, just providing a transparent
intercommunicating within local servers and remote servers we're can
get anything from anywhere if have a correct access right.
For example we're have misc binary server on the local node and we're
wants to run it on the remote node, in this case we're doing an one
request and take a connection with the ikernel, but all datas sends to
the remote node server directly.
There are more schemes for intercommunicating with a big number of
examples.
Anyway, we're working on the optimization in this part permanently,
providing to us more feature request and cases of intercommunicating
the new solutions will be done.
[Index] [Back] [Next]