24%
07.11.2011
_get_obj_by_type(topo, HWLOC_OBJ_CORE, n ‑ 1);
03 hwloc_set_cpubind(topo, obj‑>cpuset, 0);
In Listings 6 and 7, the type
and cpuset
members are just two examples of the variety of information available at each object
24%
07.11.2011
for [clauses ...]
for (i=0;i<N;i++) {
a[i]= i*i; /* parallelized */
}
... /* one thread */
Also, you can combine the two compiler directives, parallel
and sections
, to form a single directive
24%
22.08.2017
_get_wtime ( ) - wtime
write ( *, '(a)' ) ' '
write ( *, '(a)' ) ' Back OUTSIDE the parallel region.'
write ( *, '(a)' ) ' '
write ( *, '(a,g14.6)' ) ' Elapsed wall clock time = ', wtime
!
! Terminate.
!
write
24%
28.07.2025
from serial CPU logic to CPU instructions operating on multiple data (such as AVX [6]) or a GPU's finer grained parallelism. Many strategies are liable to backfire when switching the underlying choices
24%
16.10.2012
as shown in the following listing.
Apache/2.2.16 (Debian) DAV/2 SVN/1.6.12
mod_fcgid/2.3.6 Phusion_Passenger/3.0.11
mod_ssl/2.2.16 OpenSSL/0.9.8o Server at
www.domain.tld Port 80
Treacherous Error Messages
24%
10.06.2014
"ram": 2048,
07 "resolvers": ["192.168.111.254"],
08 "disks": [
09 {
10 "image_uuid": "1fc068b0-13b0-11e2-9f4e-2f3f6a96d9bc",
11 "boot": true,
12 "model": "virtio"
13 }
14
24%
30.01.2020
and IPv6 packets in the past, you not only needed different rules, you even had to load them into the kernel with different tools: iptables and ip6tables.
The simple nftables inet table type includes both
24%
13.02.2017
of around 250MB to Amazon's S3 storage very effectively. A number of successful container technologies have been used extensively in the past, including LXC, Solaris Zones, and FreeBSD jails, to name
24%
07.01.2024
press the Tab key twice, you will get a list of the filesystems mkfs
currently supports. For example, on my Ubuntu 22.04 system, I get the following output.
$ mkfs
mkfs
24%
20.06.2022
significantly more resources, which means that the scope of this attack is quite remarkable. According to Cloudflare, the botnet used for the attack consisted of 6,000 unique bots from 1,300 different networks
