diff options
| author | Francis Dupont <fdupont@isc.org> | 2019-09-26 15:12:04 +0200 |
|---|---|---|
| committer | Francis Dupont <fdupont@isc.org> | 2019-09-27 11:07:21 +0200 |
| commit | 5a36558f35edc0d55bb1d9bd88fa8deda3373c53 (patch) | |
| tree | e62a7a7d8b7f222dc253a2ac461e3008e435c514 /doc/devel | |
| parent | [907-remove-kea-thread-library] Finished netconf (diff) | |
| download | kea-5a36558f35edc0d55bb1d9bd88fa8deda3373c53.tar.xz kea-5a36558f35edc0d55bb1d9bd88fa8deda3373c53.zip | |
[907-remove-kea-thread-library] Addressed comments
Diffstat (limited to 'doc/devel')
| -rw-r--r-- | doc/devel/Doxyfile | 1 | ||||
| -rw-r--r-- | doc/devel/congestion-handling.dox | 5 |
2 files changed, 2 insertions, 4 deletions
diff --git a/doc/devel/Doxyfile b/doc/devel/Doxyfile index c3960acffd..5032a88325 100644 --- a/doc/devel/Doxyfile +++ b/doc/devel/Doxyfile @@ -814,7 +814,6 @@ INPUT = ../../src/bin/agent \ ../../src/lib/util/encode \ ../../src/lib/util/io \ ../../src/lib/util/random \ - ../../src/lib/util/threads \ ../../src/lib/util/unittests \ ../../src/lib/yang \ . diff --git a/doc/devel/congestion-handling.dox b/doc/devel/congestion-handling.dox index 058a3a7f41..e5e44fe815 100644 --- a/doc/devel/congestion-handling.dox +++ b/doc/devel/congestion-handling.dox @@ -1,4 +1,4 @@ -// Copyright (C) 2018 Internet Systems Consortium, Inc. ("ISC") +// Copyright (C) 2018-2019 Internet Systems Consortium, Inc. ("ISC") // // This Source Code Form is subject to the terms of the Mozilla Public // License, v. 2.0. If a copy of the MPL was not distributed with this @@ -111,8 +111,7 @@ isc::dhcp::PacketQueueRing6). The most critical aspects to remember when developing your implementation are: -# It MUST be thread safe since queuing and dequeing packets are done by -separate threads. (You might considering using isc::util::thread::Mutex and -isc::util::thread::Mutex::Locker). +separate threads. (You might considering using std::mutex and std::lock_guard). -# Its efficiency (or lack thereof) will have a direct impact on server performance. You will have to consider the dynamics of your deployment |