Comments (3)
It's probably easier to just say it's faster, especially for small (in terms of CPU usage) requests.
It doesn't bypass the scheduler (that'd be bad -- a nefarious process could hog some/all of the available CPUs if it did that). ISTR the net effect is that the client's remaining time slice is effectively loaned to the server thread, so either thread can still go off cpu if the time slice is exceed.
Normally, an RPC request over say a pipe or localhost socket means the client gets put on a wait queue, it has to wait until the scheduler decides to run the server process, then wait until the scheduler decides to run the client thread again (which could be a while on a busy system). With a door, the scheduler just immediately switches to the server process and then back to the client and skips all the queueing (so you could say it takes a short cut through the scheduler), though still subject to time slice limits.
from revolving-doors.
Or, instead of explaining it (which is above my head for the moment anyhow), it might be suitable to just claim that doors are faster than other forms of IPC and either cite the comparison given in the Stevens book or whip up an alternate client & server using sockets, and do the same data transfer comparison on that.
from revolving-doors.
@jasonbking thank you, that is clarifying.
from revolving-doors.
Related Issues (20)
- Adjust door message size with door_setparam HOT 3
- Clarify that door passing is a special case of descriptor passing
- 18_backgrounding_processes/server.c has door routines from next step HOT 1
- Clarify DVD / USB downloads for OpenIndiana HOT 1
- Set up a sockets demo for contrast HOT 5
- Use door revoke instead of close
- Have setup guides create an unprivileged user
- Call door_return from "main" thread instead of sleep HOT 1
- Update diagrams with inline mermaid
- Add setup guide for SmartOS on Triton
- Add Check for Understanding on A0_result_parameters
- port Makefiles to illumos make
- Showcase a DNS server with separate door servers for each DNS zone
- Add an exercise about integrating shared memory
- Finish OpenIndiana Setup Guide HOT 3
- Write SmartOS setup guide
- Prefer open over stat+creat
- Lowercase illumos
- Prefer err.h family of functions over perror+exit
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from revolving-doors.