similar to: mtrr_gran_size and mtrr_chunk_size

Hi, I have server that has been running 5.x - 5.8 for a few years without issue and decided to move it to a fresh install of 6.2. First thing I noticed is a good part of the log has these mtrr messages finally ending with "mtrr_cleanup: can not find optimal value" and "please specify mtrr_gran_size/mtrr_chunk_size". I have been searching around and reading the kernel docs

After fresh installation of CentOS 6.2 on my server, I get following errors in my dmesg output: ------- MTRR default type: uncachable MTRR fixed ranges enabled: 00000-9FFFF write-back A0000-BFFFF uncachable C0000-D7FFF write-protect D8000-E7FFF uncachable E8000-FFFFF write-protect MTRR variable ranges enabled: 0 base 000000000 mask C00000000 write-back 1 base 400000000 mask

CentOS 6.4, current, Dell PE R720. Had an issue today with a bus error, and googling only found two year old references to problems with non-Dell drives (we just added two WD Reds, and mdadm raided them). So, looking through dmesg and /var/log/messages, I ran into a *lot* of G gran_size: 128K chunk_size: 256K num_reg: 10 lose cover RAM: 0G gran_size: 128K chunk_size:

Mark II of the patch set. The first patch (dynsumlen2.patch) increments the protocol version to support per-file dynamic block checksum sizes. It is a prerequisite for varsumlen2.patch. varsumlen2.patch implements per-file dynamic block and checksum sizes. The current block size calculation only applies to files between 7MB and 160MB setting the block size to 1/10,0000 of the file length for a

When a whole-file checksum is performed, hashing was done in 64 byte blocks, causing overhead and limiting performance. Testing showed the performance improvement to go up quickly going from 64 to 512 bytes, with diminishing returns above, 4096 was where it seemed to plateau for me. Re-used CHUNK_SIZE (32 kB) as it already exists and should be fine to use here anyway. Noticed this because

$./mkfs.btrfs -f /dev/sdd -b 2M [...] mkfs.btrfs: volumes.c:845: btrfs_alloc_chunk: Assertion `!(ret)'' failed. Aborted (core dumped). We should return error to userspace instead of the above. Signed-off-by: Liu Bo <bo.li.liu@oracle.com> --- mkfs.c | 23 +++++++++++++++-------- volumes.c | 16 +++++++++++----- 2 files changed, 26 insertions(+), 13 deletions(-) diff --git

Hy Timo ! I Made some modification in stream_read in zlib. I remove all zlib part, because i don't need this, but i need to read a istream to change it. Well, i create a size_t called supersize, with is a substitute for stream->zs.avail_in. The trouble is, my debug file have a lot of "READ Plugin\n", and i think it's because my read becomes a loop, i think it's because

From: Halil Pasic <pasic at linux.ibm.com> To support protected virtualization cio will need to make sure the memory used for communication with the hypervisor is DMA memory. Let us introduce one global cio, and some tools for pools seated at individual devices. Our DMA pools are implemented as a gen_pool backed with DMA pages. The idea is to avoid each allocation effectively wasting a

From: Halil Pasic <pasic at linux.ibm.com> To support protected virtualization cio will need to make sure the memory used for communication with the hypervisor is DMA memory. Let us introduce one global pool for cio. Our DMA pools are implemented as a gen_pool backed with DMA pages. The idea is to avoid each allocation effectively wasting a page, as we typically allocate much less than

On Fri, 10 May 2019 16:10:13 +0200 Cornelia Huck <cohuck at redhat.com> wrote: > On Fri, 10 May 2019 00:11:12 +0200 > Halil Pasic <pasic at linux.ibm.com> wrote: > > > On Thu, 9 May 2019 12:11:06 +0200 > > Cornelia Huck <cohuck at redhat.com> wrote: > > > > > On Wed, 8 May 2019 23:22:10 +0200 > > > Halil Pasic <pasic at

To support protected virtualization cio will need to make sure the memory used for communication with the hypervisor is DMA memory. Let us introduce one global pool for cio. Our DMA pools are implemented as a gen_pool backed with DMA pages. The idea is to avoid each allocation effectively wasting a page, as we typically allocate much less than PAGE_SIZE. Signed-off-by: Halil Pasic <pasic at

To support protected virtualization cio will need to make sure the memory used for communication with the hypervisor is DMA memory. Let us introduce one global pool for cio. Our DMA pools are implemented as a gen_pool backed with DMA pages. The idea is to avoid each allocation effectively wasting a page, as we typically allocate much less than PAGE_SIZE. Signed-off-by: Halil Pasic <pasic at

On Wed, Aug 19, 2020 at 03:07:04PM +0100, Robin Murphy wrote: >> FWIW, I asked back in time what the plan is for non-coherent >> allocations and it seemed like DMA_ATTR_NON_CONSISTENT and >> dma_sync_*() was supposed to be the right thing to go with. [2] The >> same thread also explains why dma_alloc_pages() isn't suitable for the >> users of dma_alloc_attrs() and

Currently rsync has a bit of a problem with very large files. Dynamic block sizes were introduced to try handle that automatically if the user didn't specify a block size. Unfortunately that isn't enough and the block size would need to grow faster than the file. Besides, overly large block sizes mean large amounts of data need to be copied even for small changes. The maths indicate

On Thu, Aug 20, 2020 at 7:02 AM Christoph Hellwig <hch at lst.de> wrote: > > On Wed, Aug 19, 2020 at 03:07:04PM +0100, Robin Murphy wrote: > >> FWIW, I asked back in time what the plan is for non-coherent > >> allocations and it seemed like DMA_ATTR_NON_CONSISTENT and > >> dma_sync_*() was supposed to be the right thing to go with. [2] The > >> same

Does anybody please have any experience with the following CentOS 6 warnings in logwatch? WARNING: Kernel Errors Present ACPI Error (psargs-0359): [ ...: 1 Time(s) pci 0000:00:01.0: PCIe errors handled by OS. ...: 1 Time(s) pci 0000:00:1c.0: PCIe errors handled by OS. ...: 1 Time(s) pci 0000:00:1c.5: PCIe errors handled by OS. ...: 1 Time(s) pci 0000:00:1c.6: PCIe errors

On Mon, 27 May 2019 08:57:18 +0200 Cornelia Huck <cohuck at redhat.com> wrote: > On Thu, 23 May 2019 18:22:03 +0200 > Michael Mueller <mimu at linux.ibm.com> wrote: > > > From: Halil Pasic <pasic at linux.ibm.com> > > > > To support protected virtualization cio will need to make sure the > > memory used for communication with the hypervisor is

On Mon, 13 May 2019 15:29:24 +0200 Cornelia Huck <cohuck at redhat.com> wrote: > On Sun, 12 May 2019 20:22:56 +0200 > Halil Pasic <pasic at linux.ibm.com> wrote: > > > On Fri, 10 May 2019 16:10:13 +0200 > > Cornelia Huck <cohuck at redhat.com> wrote: > > > > > On Fri, 10 May 2019 00:11:12 +0200 > > > Halil Pasic <pasic at

On 03/08/2017 12:01 PM, Michael S. Tsirkin wrote: > On Fri, Mar 03, 2017 at 01:40:28PM +0800, Wei Wang wrote: >> From: Liang Li <liang.z.li at intel.com> >> >> The implementation of the current virtio-balloon is not very >> efficient, because the pages are transferred to the host one by one. >> Here is the breakdown of the time in percentage spent on each

Hi! We (NetBSD pkgsrc) got the following bug report: http://www.NetBSD.org/cgi-bin/query-pr-single.pl?number=18134 In short, it says that rsync-2.5.5 does not bind to a IPv4 port (it binds only to an IPv6 port) when used with rsync --daemon, making it impossible to use rsync as rsync server under NetBSD 1.5.2 Any hints on this one? Also, one patch we have in pkgsrc seems not to have been