similar to: [MODULE] COM32 module to time null-dumping a file, v1.1

From: Gene Cumm <gene.cumm at gmail.com> COM32/samples/cptime.c: A module for coarse null-dumping speed comparisons. Accepts multiple files and an option of -s (as the first option) to provide a simple output. Also computes/displays +/- 1 tick to show coarseness. Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- I'd recommend using a file that takes around 100 ticks to

On Sat, Nov 22, 2014 at 10:39 AM, Martin Str|mberg <ams at ludd.ltu.se> wrote: > Hello. > > Use the z size specifier to printf-ing size_t variables to get rid of gcc > warning > format ?%08x? expects type ?unsigned int?, but argument 2 has type ?long unsigned int? Please, add the signed-off line. > > > -- > MartinS > > diff --git

Hello. Use the z size specifier to printf-ing size_t variables to get rid of gcc warning format ?%08x? expects type ?unsigned int?, but argument 2 has type ?long unsigned int? -- MartinS diff --git a/com32/lib/syslinux/initramfs_file.c b/com32/lib/syslinux/initramfs_file.c index 7eb55b5..9f9fa75 100644 --- a/com32/lib/syslinux/initramfs_file.c +++ b/com32/lib/syslinux/initramfs_file.c @@

The attached patch to the qemu emulation of the pcnet hardware fixes several problems. It will now only read and write a transmit or receive descriptor once. It will correctly handle transmitting frames with more than two fragments. It will discard oversize frames instead of corrupting memory. I have tested all the changes I have made and even seen an improvement in receive performance from

Well, here's the read-only shell (rosh) that I've been working on. It's functional but still quite rough. My primary intention of posting it at this time is such that people have an easy way to demonstrate to themselves that the library calls I made work. This should apply as a patch to the head of the "dir" branch and the patch for c_cflag/c_lflag. The patch is only

Hi, I am trying to set up a bridge that connects 2 user mode linux (UML) machines. The bridge lets ARP traffic through, but not the IP traffic. linux:~ # brctl showmacs br0 port no mac addr is local? ageing timer 2 00:ff:7d:86:06:47 yes 0.00 3 00:ff:bc:de:07:76 yes 0.00 2 fe:fd:c0:a8:00:03 no

hello hpa, please pull git pull git://brane.itp.tuwien.ac.at/~mattems/klibc.git maks for those changes: Kyle McMartin (1): klibc-utils: add dmesg maximilian attems (2): klibc comment fix fstype: add ocfs2 support with the following diffstat README | 2 usr/Kbuild | 2 usr/kinit/fstype/fstype.c | 15 +++++++

I ran into an interesting/strange issue today. I still don''t understand what happened, but in know what fixed it. I had a situation where I could only see vblade exported devices from OFF the physical machine. It seemed that if the packets went through two ports of the bridge (instead of one port and the real interface) they got "lost". I sniffed around and failed to

The following diffs fix negative index array accesses. For the path_append diff, if the first path is empty the second path is just duplicated without a '/'. Is this correct? -Ray- Index: misc.c =================================================================== RCS file: /home/ray/openbsd/src/usr.bin/ssh/misc.c,v retrieving revision 1.64 diff -u -p -r1.64 misc.c --- misc.c 3 Aug 2006

This patch adds experimental VMDq support (AKA Netchannel2 vmq) to the ixgbe driver. This applies to the Netchannel2 tree, and should NOT be applied to the "normal" development tree. To enable VMDq functionality, load the driver with the command-line parameter VMDQ=<num queues>, as in: $ modprobe ixgbe VMDQ=8 You can then set up PV domains to use the device by modifying your VM

The correct kernel configuration for VMDq support is CONFIG_XEN_NETDEV2_VMQ, not CONFIG_XEN_NETDEV2_BACKEND. Signed-off-by: Mitch Williams <mitch.a.williams@intel.com> diff -urpN a/drivers/net/ixgbe/ixgbe.h b/drivers/net/ixgbe/ixgbe.h --- a/drivers/net/ixgbe/ixgbe.h 2009-02-06 09:03:44.000000000 -0800 +++ b/drivers/net/ixgbe/ixgbe.h 2009-02-10 14:32:57.000000000 -0800 @@ -35,7 +35,7 @@

I've got a 3.3TB ext3 on a FC3 64-bit system, running kernel 2.6.10-1.766FC3smp. I create the partition with parted 1.6.21, and I make the fs via: mkfs.ext3 -m1 -b 4096 -T largefile4 /dev/sda1 Works fine. bonnie++ running on it multiple times for days on end, no problems. However, I do the exact same setup on a RHEL4-AS i686 system, 32-bit, and the fs is totally hosed, get all kinds of

This patch series copies the core of the tapdisk process from blktap2, with updates coming from blktap2.5. Signed-off-by: Thanos Makatos <thanos.makatos@citrix.com>

Numerous how-tos all over the Internet show how one would set up a tunnel using ssh, e.g.: ssh -f -o Tunnel=ethernet <server_ip> true I was wondering if there's a way to subsequently acquire the names of the local and remote tun/tap interfaces (e.g., using the default "-w any:any") for subsequent automatic tunnel configuration, e.g.: ip link set $TapDev up ip link set

Without further adieu, I would like to announce that I've finally pushed ROSH, the Read-Only SHell, finally to the point of being reasonably usable. From: Gene Cumm <gene.cumm at gmail.com> Patch ROSH for Syslinux-4 and make it much more usable. Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- diff --git a/com32/rosh/rosh.c b/com32/rosh/rosh.c index 511fdff..bf1176f

Hi, This set of patches contains initial kexec/kdump implementation for Xen v3. Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code. However, this solution requires some changes in baremetal x86 code. First of

Hi, This set of patches contains initial kexec/kdump implementation for Xen v3. Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code. However, this solution requires some changes in baremetal x86 code. First of

Hi, This set of patches contains initial kexec/kdump implementation for Xen v3. Currently only dom0 is supported, however, almost all infrustructure required for domU support is ready. Jan Beulich suggested to merge Xen x86 assembler code with baremetal x86 code. This could simplify and reduce a bit size of kernel code. However, this solution requires some changes in baremetal x86 code. First of

From: Jason Gunthorpe <jgg at mellanox.com> 8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1, scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where they only use invalidate_range_start/end and immediately check the invalidating range against some driver data structure to tell if the driver is interested. Half of them use an interval_tree, the others

From: Jason Gunthorpe <jgg at mellanox.com> 8 of the mmu_notifier using drivers (i915_gem, radeon_mn, umem_odp, hfi1, scif_dma, vhost, gntdev, hmm) drivers are using a common pattern where they only use invalidate_range_start/end and immediately check the invalidating range against some driver data structure to tell if the driver is interested. Half of them use an interval_tree, the others