search for: hndl

...EF50L 0000400000000100 0000000000000000 ..... at .......... 00000000C78CEF60L 0000000000000001 FA1F270A06290000 ..........)..'.z 00000000C78CEF70L 0000000000000045 00000000C78CF003 E........p.G.... ip4 handle that results in EFI_UNSUPPORTED: 00000000C99E2318L 000000006C646E68 00000000C8E1DBA0 hndl.... [aH.... 00000000C99E2328L 00000000C9BC07A0 00000000C8E0C828 .<I....(H`H.... 00000000C99E2338L 00000000C99DDF28 000000000000780A (_.I.....x...... 00000000C99E2348L 0000000000000401 000000586C617470 ........ptalX... 00000000C99E2358L 7E840FE73B45017E 0002D68E0F000002 ~.E;g..~.....V.. 00000000...

...de. I can see that the same number of reading block demand (according to the sql log) follow an increasing amount of ocfs_get_block2() call. In consequence the request reponse time is dramaticaly increase. I tried to put more verbose debug trace in ocfs_create_or_open_file() in order to grab to oin.hndl releasing token, but i don't konw enough OCFS desing yet to be performant, so i write to you to have help. First question: Could you help me please ..... ;-). Second: I see in the source you use VFS dentry struture. In the RH 2.4.18 I2 kernel this structure was little modified to be more &quot...

...de. I can see that the same number of reading block demand (according to the sql log) follow an increasing amount of ocfs_get_block2() call. In consequence the request reponse time is dramaticaly increase. I tried to put more verbose debug trace in ocfs_create_or_open_file() in order to grab to oin.hndl releasing token, but i don't konw enough OCFS desing yet to be performant, so i write to you to have help. First question: Could you help me please ..... ;-). Second: I see in the source you use VFS dentry struture. In the RH 2.4.18 I2 kernel this structure was little modified to be more &quot...

...Lmbench also shows improvements in fork/exec/sh: Processor, Processes - times in microseconds - smaller is better -------------------------------------------------------------------- Host OS Mhz null null open slct sig sig fork exec sh call I/O stat clos TCP inst hndl proc proc proc --------- ------------- ---- ---- ---- ---- ---- ---- ---- ---- ---- Linux 2.6.12- 3786 1.13 1.36 3.93 6.04 10.5 1.43 4.33 536. 1446 3614 Linux 2.6.12- 3786 1.13 1.36 3.91 6.03 10.4 1.44 4.38 346. 1050 2831 Signed-off-by: Jun Nakajima <jun.nakajima@intel.com> Jun --- Intel O...

...00000000000 ..... at .......... > 00000000C78CEF60L 0000000000000001 FA1F270A06290000 ..........)..'.z > 00000000C78CEF70L 0000000000000045 00000000C78CF003 E........p.G.... > > ip4 handle that results in EFI_UNSUPPORTED: > > 00000000C99E2318L 000000006C646E68 00000000C8E1DBA0 hndl.... [aH.... > 00000000C99E2328L 00000000C9BC07A0 00000000C8E0C828 .<I....(H`H.... > 00000000C99E2338L 00000000C99DDF28 000000000000780A (_.I.....x...... > 00000000C99E2348L 0000000000000401 000000586C617470 ........ptalX... > 00000000C99E2358L 7E840FE73B45017E 0002D68E0F000002 ~.E;g...

.... > > 00000000C78CEF60L 0000000000000001 FA1F270A06290000 ..........)..'.z > > 00000000C78CEF70L 0000000000000045 00000000C78CF003 E........p.G.... > > > > ip4 handle that results in EFI_UNSUPPORTED: > > > > 00000000C99E2318L 000000006C646E68 00000000C8E1DBA0 hndl.... [aH.... > > 00000000C99E2328L 00000000C9BC07A0 00000000C8E0C828 .<I....(H`H.... > > 00000000C99E2338L 00000000C99DDF28 000000000000780A (_.I.....x...... > > 00000000C99E2348L 0000000000000401 000000586C617470 ........ptalX... > > 00000000C99E2358L 7E840FE73B45017E 00...

>>> I'm also interested on this, but I do not quite understand the problem. Could you please tell us more about this issue (Wireshark) <<< Attached is a Wireshark capture using the current commit (43f5efa) from Patrick's repo, .Syslinux.efi is downloaded, there is an ARP and then nothing hits the wire from the client. The internal failing scenario is core_udp_sendto

...ERROR_DUPLICATE_ENTRY; + } + + return result; +} + +/* + * Unregisters a queue pair handle that was previously registered + * with vmci_ctx_qp_create. + */ +int vmci_ctx_qp_destroy(struct vmci_ctx *context, + struct vmci_handle handle) +{ + struct vmci_handle hndl; + + if (context == NULL || VMCI_HANDLE_INVALID(handle)) + return VMCI_ERROR_INVALID_ARGS; + + hndl = vmci_handle_arr_remove_entry(context->queuePairArray, handle); + + return VMCI_HANDLE_INVALID(hndl) ? + VMCI_ERROR_NOT_FOUND : VMCI_SUCCESS; +} + +/...

...ERROR_DUPLICATE_ENTRY; + } + + return result; +} + +/* + * Unregisters a queue pair handle that was previously registered + * with vmci_ctx_qp_create. + */ +int vmci_ctx_qp_destroy(struct vmci_ctx *context, + struct vmci_handle handle) +{ + struct vmci_handle hndl; + + if (context == NULL || VMCI_HANDLE_INVALID(handle)) + return VMCI_ERROR_INVALID_ARGS; + + hndl = vmci_handle_arr_remove_entry(context->queuePairArray, handle); + + return VMCI_HANDLE_INVALID(hndl) ? + VMCI_ERROR_NOT_FOUND : VMCI_SUCCESS; +} + +/...

Hi ! Kenrel 2.6.21 (kernel.org) Patch lguest-2.6.21-254.patch Distro Slackware 11.0 GCC 3.4.6 GLIBC 2.3.6 HW model name : AMD Duron(tm) procu{s{ Module Size Used by tun 7680 0 lg 54600 0 just started playing with lguest - patching, compiling and booting the host-kernel goes ok - compiling lguest is ok as well after

Hi ! Kenrel 2.6.21 (kernel.org) Patch lguest-2.6.21-254.patch Distro Slackware 11.0 GCC 3.4.6 GLIBC 2.3.6 HW model name : AMD Duron(tm) procu{s{ Module Size Used by tun 7680 0 lg 54600 0 just started playing with lguest - patching, compiling and booting the host-kernel goes ok - compiling lguest is ok as well after

In OLS 2005, we described the work that we have been doing in VMware with respect a common interface for paravirtualization of Linux. We shared the general vision in Rik's virtualization BoF. This note is an update on our further work on the Virtual Machine Interface, VMI. The patches provided have been tested on 2.6.16-rc6. We are currently recollecting performance information for the new

In OLS 2005, we described the work that we have been doing in VMware with respect a common interface for paravirtualization of Linux. We shared the general vision in Rik's virtualization BoF. This note is an update on our further work on the Virtual Machine Interface, VMI. The patches provided have been tested on 2.6.16-rc6. We are currently recollecting performance information for the new

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012

* * * 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

* * * 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

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.