search for: removeentry

...s R to hang: match(c("A", "B", "C"), "A", incomparables=NA) I found the reason in the hash table implementation in unique.c. Values in the table argument of match are stored in a hash table. Incomparables are then removed by (potentially multiple) calls to removeEntry(): static void removeEntry(SEXP table, SEXP x, int indx, HashData *d) { int i, *h; h = INTEGER(d->HashTable); i = d->hash(x, indx, d); while (h[i] != NIL) { if (d->equal(table, h[i], x, indx)) { h[i] = NA_INTEGER; /* < 0, only index values are inserted */...

.../* + * Remove entry from hash table if not already + * removed. This could have happened already because + * vmci_hash_remove was called to unlink it. We ignore + * if it is not found. Datagram handles will often + * have RemoveEntry called, whereas SharedMemory + * regions rely on ReleaseEntry to unlink the entry, + * since the creator does not call RemoveEntry when it + * detaches. + */ + hash_unlink(table, entry); + result = VMCI_SUCCESS_...

.../* + * Remove entry from hash table if not already + * removed. This could have happened already because + * vmci_hash_remove was called to unlink it. We ignore + * if it is not found. Datagram handles will often + * have RemoveEntry called, whereas SharedMemory + * regions rely on ReleaseEntry to unlink the entry, + * since the creator does not call RemoveEntry when it + * detaches. + */ + hash_unlink(table, entry); + result = VMCI_SUCCESS_...

Second revision of the VMware VMCI RFC patchset. It incorperates fixes for all the feedback about the comment blocks and style and now passes checkpatch with 0 errors and 0 warnings. Thanks to all who have reviewed the code thus far. * * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication

Second revision of the VMware VMCI RFC patchset. It incorperates fixes for all the feedback about the comment blocks and style and now passes checkpatch with 0 errors and 0 warnings. Thanks to all who have reviewed the code thus far. * * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.