File: control

package info (click to toggle)
libmmap-allocator 0.4.0%2Bgit20200122.adbfbe1-1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm, bullseye
  • size: 152 kB
  • sloc: cpp: 946; ansic: 61; makefile: 44; sh: 11
file content (31 lines) | stat: -rw-r--r-- 1,411 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Source: libmmap-allocator
Maintainer: Debian Med Packaging Team <debian-med-packaging@lists.alioth.debian.org>
Uploaders: Andreas Tille <tille@debian.org>
Section: libdevel
Priority: optional
Build-Depends: debhelper-compat (= 13),
               dh-exec
Standards-Version: 4.5.0
Vcs-Browser: https://salsa.debian.org/med-team/libmmap-allocator
Vcs-Git: https://salsa.debian.org/med-team/libmmap-allocator.git
Homepage: https://github.com/ekg/mmap_allocator/

Package: libmmap-allocator-dev
Architecture: any
Depends: ${shlibs:Depends},
         ${misc:Depends}
Description: STL allocator that mmaps files
 When reading large files (>100MB) into memory, read() calls are usually
 not very space and time efficient, since the whole data is copiied at
 least once. Furthermore, when using STL containers (like a vector for
 example), data is copiied another time unless the location of the vector
 content as parameter to read() will be specified.
 .
 It would be nice to tell the vector a filename and have the vector mmap
 the file directly. This not only avoids the read() copiing (and the STL
 vector copiing) but also allows different processes that read the same
 file to see the same physical memory. Fortunately STL foresees an
 interface to do exactly this.
 .
 Libmmap-allocator helps to handle big files that contain unstructured
 data (like doubles or even text files), mmap_allocator is worth a try.