diff options
Diffstat (limited to 'debian/patches/0001-libports-use-a-single-hash-table.patch')
| -rw-r--r-- | debian/patches/0001-libports-use-a-single-hash-table.patch | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/debian/patches/0001-libports-use-a-single-hash-table.patch b/debian/patches/0001-libports-use-a-single-hash-table.patch index 492a4cab..ec0af1b9 100644 --- a/debian/patches/0001-libports-use-a-single-hash-table.patch +++ b/debian/patches/0001-libports-use-a-single-hash-table.patch @@ -1,15 +1,15 @@ -From 27741dca90e3a6070727fffc22d3105653a33747 Mon Sep 17 00:00:00 2001 +From ad5c0b3331c73bae11c0c9da422ffd190a0dccfc Mon Sep 17 00:00:00 2001 From: Justus Winter <4winter@informatik.uni-hamburg.de> Date: Sat, 3 May 2014 03:53:41 +0200 -Subject: [PATCH 1/5] libports: use a single hash table +Subject: [PATCH 01/11] libports: use a single hash table Previously, libports used a hash table per port bucket. This makes looking up a port difficult if one does not know the port bucket, as one has to iterate over all buckets and do a hash table lookup each. -The having to iterate over the buckets makes it necessary to keep a -list of all buckets, which has to be updated and protected by a lock -as well. +Having to iterate over the buckets makes it necessary to keep a list +of all buckets, which has to be updated and protected by a lock as +well. Also, the current code in _ports_bucket_class_iterate iterates over the hash table associated with the bucket given. When |