Re: Spinlock performance improvement proposal
От | mlw |
---|---|
Тема | Re: Spinlock performance improvement proposal |
Дата | |
Msg-id | 3BB53F68.3270BB17@mohawksoft.com обсуждение исходный текст |
Ответ на | Spinlock performance improvement proposal (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Spinlock performance improvement proposal
|
Список | pgsql-hackers |
Bruce Momjian wrote: > > > Save for the fact that the kernel can switch between threads faster then > > it can switch processes considering threads share the same address space, > > stack, code, etc. If need be sharing the data between threads is much > > easier then sharing between processes. > > Just a clarification but because we fork each backend, don't they share > the same code space? Data/stack is still separate. In Linux and many modern UNIX programs, you share everything at fork time. The data and stack pages are marked "copy on write" which means that if you touch it, the processor traps and drops into the memory manager code. A new page is created and replaced into your address space where the page, to which you were going to write, was.
В списке pgsql-hackers по дате отправления: