search for: containerized

...is week and the vector types seem > > to be inside structures. If vector types are considered proper types > > in LLVM, why pack them inside structures? > > Because that is what ARM has specified? They define the vector types > that are used with their NEON intrinsics as "containerized vectors". > Perhaps someone on the list from ARM can explain why they did it that > way. "Containerized Vector" in the ARM AAPCS refers to fundamental data types (machine types), it's the class of machine types comprising the 64-bit and 128-bit NEON machine types. The AAP...

Folks: This is **off topic**, but I thought it might be informative to this community. Consequently: please **no on list public comments or discussion**. Feel free to respond to me privately, if you like; but I have neither knowledge nor opinions, so why bother? This is just FYI. My apology if it is deemed inappropriate. http://www.nature.com/news/software-simplified-1.22059 Cheers, Bert Bert

This is a nice summary addressing the same with R: https://arxiv.org/pdf/1410.0846.pdf On 30 May 2017 at 17:43, Bert Gunter <bgunter.4567 at gmail.com> wrote: > Folks: > > This is **off topic**, but I thought it might be informative to this > community. Consequently: please **no on list public comments or > discussion**. Feel free to respond to me privately, if you like; but

...ing NEON instructions this week and the vector types seem > to be inside structures. If vector types are considered proper types > in LLVM, why pack them inside structures? Because that is what ARM has specified? They define the vector types that are used with their NEON intrinsics as "containerized vectors". Perhaps someone on the list from ARM can explain why they did it that way. The extra structures are irrelevant at the llvm IR level and below. The NEON intrinsics in llvm use plain old vector types. If you're using llvm-gcc, you can define the ARM_NEON_GCC_COMPATIBILITY prepr...

...or types seem >> > to be inside structures. If vector types are considered proper types >> > in LLVM, why pack them inside structures? >> >> Because that is what ARM has specified?  They define the vector types >> that are used with their NEON intrinsics as "containerized vectors". >> Perhaps someone on the list from ARM can explain why they did it that >> way. > > "Containerized Vector" in the ARM AAPCS refers to fundamental data > types (machine types), it's the class of machine types comprising > the 64-bit and 128-bit N...

Second question: I was checking NEON instructions this week and the vector types seem to be inside structures. If vector types are considered proper types in LLVM, why pack them inside structures? That results in a lot of boilerplate code for converting and copying the values (about 20 lines of IR) just to call a NEON instruction that, in the end, will be converted into three instructions: VLDR

On 21 September 2010 18:03, Bob Wilson <bob.wilson at apple.com> wrote: > Because that is what ARM has specified?  They define the vector types that are used with their NEON intrinsics as "containerized vectors".  Perhaps someone on the list from ARM can explain why they did it that way. That's ok, but why do you need to do that in the IR? I mean, in the end, the boilerplate will be optimized away and all that's left will be the vector instruction, either compiled or JITed. > As...

==================================================================== CALL FOR PAPERSa 15th Workshop on Virtualization in High-Performance Cloud Computing (VHPC 20) held in conjunction with the International Supercomputing Conference - High Performance, June 21-25, 2020, Frankfurt, Germany. (Springer LNCS Proceedings) ==================================================================== Date:

==================================================================== CALL FOR PAPERS 15th Workshop on Virtualization in High-Performance Cloud Computing (VHPC 20) held in conjunction with the International Supercomputing Conference - High Performance, June 21-25, 2020, Frankfurt, Germany. (Springer LNCS Proceedings) ==================================================================== Date:

On 7/3/19 8:21 AM, Sven Schwedas via samba wrote: > Though I'm not sure if docker is the right tool for the job; samba as a > fat daemon running a bazillion subprocesses orchestrated by a persistent > database that's very sensitive to instances leaving and joining the > domain seems the antithesis to docker's philosophy. > Docker would be a terrible choice for this;

==================================================================== CALL FOR PAPERS 15th Workshop on Virtualization in High-Performance Cloud Computing (VHPC 20) held in conjunction with the International Supercomputing Conference - High Performance, June 21-25, 2020, Frankfurt, Germany. (Springer LNCS Proceedings) ==================================================================== Date:

On 7/4/19 12:49 PM, Joachim Lindenberg wrote: > * I am not (yet) familiar with LXD or nspawn. Do you have any pointer on how Samba DC works with LXD? > I've only used LXD for containerizing web applications so far.

On Sep 21, 2010, at 10:14 AM, Renato Golin wrote: > On 21 September 2010 18:03, Bob Wilson <bob.wilson at apple.com> wrote: >> Because that is what ARM has specified? They define the vector types that are used with their NEON intrinsics as "containerized vectors". Perhaps someone on the list from ARM can explain why they did it that way. > > That's ok, but why do you need to do that in the IR? I mean, in the > end, the boilerplate will be optimized away and all that's left will > be the vector instruction, either compiled...

Hi, I've been doing some research and testing into implementing SAMBA 4 as a AD/DC role for offering "AD as a service" to various small companies, I've been testing SAMBA out in various different configurations and wondering if SAMBA in AD/DC role if it's possible to segment in such a way some requirements: - Windows 10 support, e.g SMB3 - AD tree segmentation so that one

...ings volume. Topics of Interest The VHPC program committee solicits original, high-quality submissions related to virtualization across the entire software stack with a special focus on the intersection of HPC, containers-virtualization and the cloud. Major Topics: - HPC on Containers and VMs - Containerized applications with OS-level virtualization - Lightweight applications with Unikernels - HP-as-a-Service each major topic encompassing design/architecture, management, performance management, modeling and configuration/tooling: Design / Architecture: - Containers and OS-level virtualization (LXC, D...

...ings volume. Topics of Interest The VHPC program committee solicits original, high-quality submissions related to virtualization across the entire software stack with a special focus on the intersection of HPC, containers-virtualization and the cloud. Major Topics: - HPC on Containers and VMs - Containerized applications with OS-level virtualization - Lightweight applications with Unikernels - HP-as-a-Service each major topic encompassing design/architecture, management, performance management, modeling and configuration/tooling: Design / Architecture: - Containers and OS-level virtualization (LXC, D...

...volume. Topics of Interest The VHPC program committee solicits original, high-quality submissions related to virtualization across the entire software stack with a special focus on the intersection of HPC, containers-virtualization and the cloud. Major Topics: - HPC on Containers and VMs - Containerized applications with OS-level virtualization - Lightweight applications with Unikernels - HP-as-a-Service each major topic encompassing design/architecture, management, performance management, modeling and configuration/tooling: Design / Architecture: - Containers and OS-level virtualization (LX...

...volume. Topics of Interest The VHPC program committee solicits original, high-quality submissions related to virtualization across the entire software stack with a special focus on the intersection of HPC, containers-virtualization and the cloud. Major Topics: - HPC on Containers and VMs - Containerized applications with OS-level virtualization - Lightweight applications with Unikernels - HP-as-a-Service each major topic encompassing design/architecture, management, performance management, modeling and configuration/tooling: Design / Architecture: - Containers and OS-level virtualization (LX...

Hi, the instructions for "Time Synchronisation - SELinux Labeling and Policy" on https://wiki.samba.org/index.php/Time_Synchronisation_-_SELinux_Labeling_and_Policy don't seem to work on CentOS 8. Using chrony I tried to adapt them (with very limited SELinux knowledge) like this: chcon -u system_u -t chronyd_exec_t /var/lib/samba/ntp_signd semanage fcontext -a -t chronyd_exec_t

https://github.com/kubevirt/containerized-data-importer/issues/1520 Hi Eric, We had a question from the Kubevirt team related to the above issue. The question is roughly if it's possible to calculate the checksum of an image as an nbdkit filter and/or in the qemu block layer. Supplemental #1: could qemu-img convert calculate a check...