search for: 48s

...+ int index = 0; + uint8_t *p = data; + uint8_t hex[16 * 3 + 1] = {0, }; + uint8_t text[16 + 1] = {0, }; + uint8_t c; + + for (i = 0; i < len; i++) { + index = i & 0xf; + if (i && index == 0) { + /* print the buffer before reset it */ + printf("%08x %-48s |%-16s|\n", base, hex, text); + base += 0x10; + memset(hex, 0, sizeof hex); + memset(text, 0, sizeof text); + } + + c = *p++; + sprintf((char *)&hex[index * 3], "%02x ", c); + if (c < 0x20 || c > 0x7f) + text[index] = '.'; + else + text[index] =...

...pshot Home-2013.01.17-05.07.02, size 1.0T Logical volume "Home-2013.01.17-05.07.02" created Oldest Snapshot = Home-2013.01.16-05.07.03, @/home/.snapdir/@GMT-2013.01.16-05.07.03 Performing rsync with 7 excludes used from config file. rsync took 115m, 11s Empty-directory removal took 0m, 48s Find size of dir @ /home.diff size=14248587264, minsize=17098304717, extent_size=4194304, nextents=4077 Old volume active: Deactivated. Removed. size=17100177408 Create vol. Home-2013.01.16-05.07.03, size 15.9G Logical volume "Home-2013.01.16-05.07.03" created About to copy base-diff d...

Hello, I'm writng this message to see if anyone knows how to analyze a data with geometrically distributed outcome. My situation now is : I have a outcome which is geometrically distributed. And I've also self-derived the link function for geometric distribution. I want to use generalized linear models to analyze it, but there're only models for binary data, poisson distributed

...vendorid: 04b4 / /$systemctl status nut-server.service ? nut-server.service - Network UPS Tools - power devices information server ???? Loaded: loaded (/lib/systemd/system/nut-server.service; enabled; vendor preset: enabled) ???? Active: active (running) since Wed 2024-03-27 12:04:45 CET; 3min 48s ago ??? Process: 17682 ExecStart=/sbin/upsd (code=exited, status=0/SUCCESS) ?? Main PID: 17683 (upsd) ????? Tasks: 1 (limit: 19016) ???? Memory: 620.0K ??????? CPU: 32ms ???? CGroup: /system.slice/nut-server.service ???????????? ??17683 /lib/nut/upsd mars 27 12:04:45 nicolas-MS-7B19 systemd...

I have a data frame in long format and I would like to randomly divide this data frame in half. The data frame consists of 39622 rows and I initially tried ... randomsample1 <- data[sample(nrow(data),19811), ] Where allows me to randomly select half of the rows and assign them to randomsample1 but then I couldn't figure out how to select those rows that were not selected and assign

Hey all, I was watching some logs on a domU today and i suddenly noticed that the timestamps were off by something on the order of 47 seconds. I was surprised because *I don''t* run independent wall clocks. I checked some other domUs and the "drift" was also very close to that of the first domU. I also checked another dom0, Here the domUs were "only" out of sync by

Hello all/Timo, Up until now, my main Clients office has consisted of a single location, and I have never had to deal with the situation of multiple locations for a single company. They have just told me that they are acquiring an additional floor at a building that is about 4 minutes away - but obviously far enough away that I now have to deal with supporting users in the same domain but at

So I found all 20 bytes and changed then to GHASH_SIZE (a const I defined in typehashing.h) and finished the switch to xxHash64, that saved me around 50 seconds to 56s, then I changed it to uint64_t instead of a 8 byte uint_8 array and that gave me 48s. With release config and a pgo pass I'm now linking in 38s... so faster than link.exe in vs 2017 (which is faster than vs 2015) doing fastlink. Now we are in a very good place, still not as fast as an incremental link, but generating better code and a full pdb. Do you want any of these patche...

...agada at gmail.com> wrote: > So I found all 20 bytes and changed then to GHASH_SIZE (a const I > defined in typehashing.h) and finished the switch to xxHash64, that > saved me around 50 seconds to 56s, then I changed it to uint64_t > instead of a 8 byte uint_8 array and that gave me 48s. With release > config and a pgo pass I'm now linking in 38s... so faster than > link.exe in vs 2017 (which is faster than vs 2015) doing fastlink. > > Now we are in a very good place, still not as fast as an incremental > link, but generating better code and a full pdb. > &gt...

...rote: >> >> So I found all 20 bytes and changed then to GHASH_SIZE (a const I >> defined in typehashing.h) and finished the switch to xxHash64, that >> saved me around 50 seconds to 56s, then I changed it to uint64_t >> instead of a 8 byte uint_8 array and that gave me 48s. With release >> config and a pgo pass I'm now linking in 38s... so faster than >> link.exe in vs 2017 (which is faster than vs 2015) doing fastlink. >> >> Now we are in a very good place, still not as fast as an incremental >> link, but generating better code and...

Hello all, In https://www.youtube.com/watch?v=qq0q1hfzidg, Adam Nemet (cc'ed) describes optimization remarks and some future plans for the project. I had a few follow-up questions: 1. As an example of future work to be done, the talk mentions expanding the set of optimization passes that emit remarks. However, the Clang User Manual mentions that "optimization remarks do not really make

Uhmm I changed only type hashing... Ok back to trying it again. Let's me find where it is looking at 20 bytes instead of using the size of global type hash. On 30 Jan 2018 21:33, "Zachary Turner" <zturner at google.com> wrote: > Did you change both the compiler and linker (or make sure that your > objcopy was updated to write your 64 bit hashes)? > > The linker is

...+-814 /lib/systemd/systemd-logind $ sudo systemctl status samba-ad-dc -n 500 ? samba-ad-dc.service - Samba Active Directory Domain Controller    Loaded: loaded (/lib/systemd/system/samba-ad-dc.service; enabled; vendor preset: enabled)    Active: active (running) since Sun 2019-01-06 18:27:50 CST; 48s ago   Process: 1151 ExecStart=/usr/local/samba/sbin/samba -D (code=exited, status=0/SUCCESS)  Main PID: 1171 (samba)     Tasks: 23 (limit: 4915)    CGroup: /system.slice/samba-ad-dc.service            +-1171 samba: root process .            +-1286 samba: task[s3fs_parent] .            +-1288 samba:...

Did you change both the compiler and linker (or make sure that your objcopy was updated to write your 64 bit hashes)? The linker is hardcodes to expect 20-byte sha 1s , anything else and it will recompute them in serial On Tue, Jan 30, 2018 at 12:28 PM Leonardo Santagada <santagada at gmail.com> wrote: > Nice and why are you trying blake2 instead of a faster hash algorithm? And > do