similar to: How can I watch IO operations with dtrace on zfs?

Here is a partial patch that I'm using to illustrate a few questions that I have. Looking at the gpllib write_sectors (com32/gpllib/disk/write.c) it looks like the allocated size is wrong; size is in sectors so we should adjust the alloc/memcpy by size*SECTOR. Also, comparing core/diskio.c it looks like the registers aren't even setup right. In the patch below I put an #if 0 around the

On 10/13/2010 08:36 AM, syslinux-bot for Michal Soltys wrote: > Commit-ID: 9c8db7560e2dc83d1191bb2f90b4d4d0ae3d37d6 > Gitweb: http://syslinux.zytor.com/commit/9c8db7560e2dc83d1191bb2f90b4d4d0ae3d37d6 > Author: Michal Soltys <soltys at ziu.info> > AuthorDate: Wed, 13 Oct 2010 10:57:36 +0200 > Committer: Michal Soltys <soltys at ziu.info> > CommitDate: Wed, 13

Hi, I have been doing some diskIO bench-marking of dom0 and domU (HVM). I ran into an issue where domU performed better than dom0. So I ran few experiments to check if it is just diskIO performance. I have an archlinux (kernel 3.5.0) + xen 4.2.2) installed on a Intel Core i7 Q720 machine. I have also installed archlinux (kernel 3.5.0) in domU running on this machine. The domU runs with 8 vcpus.

Hello, We found that fsync and fdatasync syscalls sometimes don't sync data in an ext3 file system under the following conditions. 1. Kernel version is 2.6.6 or later (including 2.6.8.1 and 2.6.9-rc2). 2. Ext3's journalling mode is "data=journal". 3. Create a file (whose size is 1Mbytes) and execute umount/mount. 4. lseek to a random position within the file, write 8192 bytes

Hi, Sorry for writing so many messages. I am doing a license review for syslinux in Debian and I've stumbled on the following files: * efi/console.c * efi/derivative.c * efi/diskio.c * efi/main.c * efi/mem.c * efi/pxe.c * efi/tcp.c * efi/udp.c All of them start with /* * Copyright 2011-2014 Intel Corporation - All Rights Reserved */ with no further indication of any license. This

From: Raphael S. Carvalho <raphael.scarv at gmail.com> My commit 09f4ac33 broke 'com32/lib/syslinux/disk.c' __lowmem doesn't work for declarations outside the core. Using __lowmem outside the core wouldn't have the desired effect, then lmalloc must be used instead to store dapa into the correct section (".lowmem"). Reported-by: Dark Raven <drdarkraven at

I've been playing with the Win32 SYSLINUX, and it fails if you're not using NT or 2K or XP. There are some differences when using it under Win95/98/ME, but is there any reason that this program couldn't just have a different codepath for those older version of Windows? Alex Pavloff - apavloff at esatechnology.com ESA Technology ---- www.esatechnology.com ------- Linux-based

The disk number is set twice in diskio.c/edd_rdwr_sectors() this patch removes the redundant setting. diff --git a/core/fs/diskio.c b/core/fs/diskio.c index 481b59b..38d3da3 100644 --- a/core/fs/diskio.c +++ b/core/fs/diskio.c @@ -163,8 +163,6 @@ static int edd_rdwr_sectors(struct disk *disk, void *buf, memset(&reset, 0, sizeof reset); - ireg.edx.b[0] = disk->disk_number; -

This set of patches add some support for sector size >512. Currently it fixes extlinux, MBR for GPT and ext partitions. Other code is unaffected. This set of patches has been tested on a read Dell machine running a beta firmware.

From: Raphael S. Carvalho <raphael.scarv at gmail.com> Most of file system drivers initialize the cache themselves. The problem is that the same cache could be again initialized later, then invalidating the previous one. This patch fixes this. Problem found while auditing the code. Signed-off-by: Raphael S. Carvalho <raphael.scarv at gmail.com> --- core/fs/cache.c | 2 ++

This is part of some patches to support sectors > 512. Currently I'm able to boot a Ubuntu kernel but seems that mboot is not working for some reason. This patch add a rdwr_bytes functions which remove the assumption in some places that sector is 512. This function is quite helpful if you are going to read/write a range of bytes to/from the stack without creating stack overflows for free.

From: Raphael S. Carvalho <raphael.scarv at gmail.com> MULTIFS SYNTAX: (hd[disk number]:[partition number])/path/to/file The meaning of this_fs was changed to improve the flexibility of the support. Now, this_fs means the file system being currently used. root_fs was created to save the context of the main file system (where ldlinux.sys lives in). get_fs_info is a function pointer that

On 16 Jul 2019, at 11.15, Ralf Hildebrandt via dovecot <dovecot at dovecot.org> wrote: > > * Timo Sirainen via dovecot <dovecot at dovecot.org>: > >>> And alas, I had a look at the monitoring and found that disk IO has >>> increase A LOT after the update: https://www.arschkrebs.de/images/dovecot-disk-io-increase.png >>> >>> I zoomed in

So last week I was wondering if XFS was still working -- even with its last on-disk structure changes -- and it _suprisingly_ worked as expected. Right, now I can finally get rid of GRUB and use Syslinux to boot my Linux on EFI from a rootfs with xfs. Shit, I have two partitions (the first one being the required ESP) so there is no way to access the other partitions since because Syslinux does not

On Sat, 29 Jun, at 01:57:58AM, Igor Sverkos wrote: > Hi, > > Matt Fleming wrote: > > On Tue, 25 Jun, at 01:52:00PM, Helmut Hullen wrote: > >> Thanks - now it crashes later ... > > > > What crash are you seeing? > > > >> I don't have the ia64 files which are needed for a complete binary. But > >> maybe that's only my special

I'm trying to use systemtap to monitor per process diskio performance, however when trying to start stap it says I need kernel debug packages installed. Where can I find the kernel-xen-debuginfo and kernel-debuginfo-common packages for 5.1? Greets, Chris -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Sun, Oct 29, 2017 at 5:18 PM, Lukas Schwaighofer via Syslinux <syslinux at zytor.com> wrote: > Hi, > > Sorry for writing so many messages. I am doing a license review for > syslinux in Debian and I've stumbled on the following files: > * efi/console.c > * efi/derivative.c > * efi/diskio.c > * efi/main.c > * efi/mem.c > * efi/pxe.c > * efi/tcp.c

Hi, Matt Fleming wrote: > 'make efi64' will build just for x86-64. Likewise, 'make efi32' will > build just for i386. You can combine these, so to build BIOS and efi64 > you'd do, > > make bios efi64 'make efi64' failed with: ld -T /tmp/syslinux/efi/x86_64/syslinux.ld -Bsymbolic -pie -nostdlib -znocombreloc -L/usr/lib64 --hash-style=gnu -m elf_x86_64

I''ve been getting a compile error when building the ''next-rc'' branch of btrfs-unstable. CC fs/btrfs/disk-io.o fs/btrfs/disk-io.c: In function ‘btree_migratepage’: fs/btrfs/disk-io.c:716: error: called object ‘0u’ is not a function make[2]: *** [fs/btrfs/disk-io.o] Error 1 make[1]: *** [fs/btrfs] Error 2 make: *** [fs] Error 2 Line 716 of fs/btrfs/disk-io.c is:

Now at 36 hours since zdb process start and: PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP 827 root 4936M 4931M sleep 59 0 0:50:47 0.2% zdb/209 Idling at 0.2% processor for nearly the past 24 hours... feels very stuck. Thoughts on how to determine where and why? -- This message posted from opensolaris.org