From a76d046b2f8155ada2f347f03ef400d760a9a238 Mon Sep 17 00:00:00 2001 From: vorlon Date: Sun, 20 Jul 2008 08:39:10 +0000 Subject: merge samba 3.2 experimental branch to unstable git-svn-id: svn://svn.debian.org/svn/pkg-samba/trunk/samba@2053 fc4039ab-9d04-0410-8cac-899223bdd6b0 --- docs/htmldocs/Samba3-Developers-Guide/architecture.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'docs/htmldocs/Samba3-Developers-Guide/architecture.html') diff --git a/docs/htmldocs/Samba3-Developers-Guide/architecture.html b/docs/htmldocs/Samba3-Developers-Guide/architecture.html index a21c2886f3..e076bd6181 100644 --- a/docs/htmldocs/Samba3-Developers-Guide/architecture.html +++ b/docs/htmldocs/Samba3-Developers-Guide/architecture.html @@ -1,4 +1,4 @@ -Chapter 3. Samba Architecture
Chapter 3. Samba Architecture
Prev Part II. Samba Basics Next

Chapter 3. Samba Architecture

Dan Shearer

November 1997

Table of Contents

Introduction
Multithreading and Samba
Threading smbd
Threading nmbd
nbmd Design

Introduction

+Chapter 3. Samba Architecture

Chapter 3. Samba Architecture
Prev Part II. Samba Basics Next

Chapter 3. Samba Architecture

Dan Shearer

November 1997

Table of Contents

Introduction
Multithreading and Samba
Threading smbd
Threading nmbd
nbmd Design

Introduction

This document gives a general overview of how Samba works internally. The Samba Team has tried to come up with a model which is the best possible compromise between elegance, portability, security @@ -9,7 +9,7 @@ It also tries to answer some of the frequently asked questions such as:

  1. Is Samba secure when running on Unix? The xyz platform? What about the root priveliges issue? -

  2. Pros and cons of multithreading in various parts of Samba

  3. Why not have a separate process for name resolution, WINS, and browsing?

Multithreading and Samba

+

  • Pros and cons of multithreading in various parts of Samba

  • Why not have a separate process for name resolution, WINS, and browsing?

    • Multithreading and Samba

    People sometimes tout threads as a uniformly good thing. They are very nice in their place but are quite inappropriate for smbd. nmbd is another matter, and multi-threading it would be very nice. @@ -26,7 +26,7 @@ smbd multi-threaded. Multi-threading would actually make Samba much slower, less scalable, less portable and much less robust. The fact that we use a separate process for each connection is one of Samba's biggest advantages. -

    Threading smbd

    +

    Threading smbd

    A few problems that would arise from a threaded smbd are:

    1. It's not only to create threads instead of processes, but you @@ -51,7 +51,7 @@ A few problems that would arise from a threaded smbd are:

    2. we couldn't use the system locking calls as the locking context of fcntl() is a process, not a thread. -

    Threading nmbd

    +

    Threading nmbd

    This would be ideal, but gets sunk by portability requirements.

    Andrew tried to write a test threads library for nmbd that used only @@ -78,7 +78,7 @@ packet that arrives. Having a pool of processes is possible but is nasty to program cleanly due to the enormous amount of shared data (in complex structures) between the processes. We can't rely on each platform having a shared memory system. -

    nbmd Design

    +

    nbmd Design

    Originally Andrew used recursion to simulate a multi-threaded environment, which use the stack enormously and made for really confusing debugging sessions. Luke Leighton rewrote it to use a -- cgit v1.2.3