search for: mincore

Displaying 14 results from an estimated 14 matches for "mincore".

Did you mean: micore
2011 Jan 04
16
[PATCH v2 0/5] add new ioctls to do metadata readahead in btrfs
...fragmented disk space and metadata read is a sync operation, which impacts the efficiency of readahead much. The patches try to add meatadata readahead for btrfs. In btrfs, metadata is stored in btree_inode. Ideally, if we could hook the inode to a fd so we could use existing syscalls (readahead, mincore or upcoming fincore) to do readahead, but the inode is hidden, there is no easy way for this from my understanding. So we add two ioctls for this. One is like readahead syscall, the other is like micore/fincore syscall. Under a harddisk based netbook with Meego, the metadata readahead reduced abo...
2010 Nov 23
1
[RFC PATCH] fadvise support in rsync
...uires that rsync do some accounting, calling fdatasync() and fadvise() only after giving the kernel an opportunity to flush the data itself. Moreover, fadvise(DONTNEED) frees pages regardless of whether the hinting process is the only referrer. For this reason, the previous fadvise patch also used mincore to identify which pages are needed by other processes. Altogether, this makes using fadvise very expensive from a complexity standpoint. This is very unfortunately since the interface could be quite usable with a few minor changes. I recently asked about this on the LKML[2], where Minchan Kim was...
2011 Apr 08
1
Package mice: Error in if (meth[j] != "") { : argument is of length zero
Dear R users, I am using package mice and I am getting the error " Error in if (meth[j] != "") { : argument is of length zero." I have tried using several different versions of R (even the one that will be coming out this month) to no avail. I am using RStudio as my interface with R. Also note that I had run this a couple of days ago and it was working fine; I can't,
2019 Feb 04
5
security implications of caching with virtio pmem (was Re: [PATCH v3 0/5] kvm "virtio pmem" device)
...cussed in the paper - could be modify the applications to lock the security relevant pages in memory. Again this becomes impractical with pmem as host does not have visibility into that. However note that as long as the only countermeasure linux uses is "Privileged Access" (i.e. blocking mincore) nothing can be done as guest page cache remains as vulnerable as host page cache. Countermeasures: which host-side countermeasures can be designed would depend on which countermeasures are used guest-side - we would need to make sure they are not broken by pmem. For "Preventing Efficient E...
2010 Dec 20
7
DO NOT REPLY [Bug 7876] New: please implement o_direct
https://bugzilla.samba.org/show_bug.cgi?id=7876 Summary: please implement o_direct Product: rsync Version: 3.1.0 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: costinel at gmail.com QAContact:
2007 May 07
1
Announce: rsync fadvise (cache dropping) patch updated
Hi List, I have updated my rsync fadvise patch which stops rsync from ousting all your other data from cache when running large jobs. I have also written an article about the whole issue. http://insights.oetiker.ch/linux/fadvise.html cheers tobi -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten http://it.oetiker.ch tobi@oetiker.ch ++41 62 213 9902
2011 Apr 01
0
package MICE, squeeze function, calling several variables at once
Hello everyone!I have a data set with missing observations that I am trying to impute. I am using MICE and I would like the imputed values to all be positive. I have two types of variables: prices (P1 to P136) and quantities (Q1 to Q136) and I also want the range of these two types to be different. Besides these variables. I am using the squeeze function but I am unable to set it such that I
2019 Feb 06
0
security implications of caching with virtio pmem (was Re: [PATCH v3 0/5] kvm "virtio pmem" device)
...- could be modify the applications to lock the security > relevant pages in memory. Again this becomes impractical with pmem as > host does not have visibility into that. However note that as long > as the only countermeasure linux uses is "Privileged Access" > (i.e. blocking mincore) nothing can be done as guest page cache > remains as vulnerable as host page cache. This sounds very use-case specific. If I run a VM only with a very specific workload (say, a container running one application), I usually don't care about leaks within the VM. At least not leaks between ap...
2010 Nov 04
4
fadvise DONTNEED implementation (or lack thereof)
...ses my entire 50GB home directory. I was surprised to find that rsync does not use fadvise to notify the kernel of its use-once data usage pattern. It looks like a patch[1] was written (although never merged, it seems) incorporating fadvise support, but I found its implementation rather odd, using mincore() and FADV_DONTNEED to kick out only regions brought in by rsync. It seemed to me the simpler and more appropriate solution would be to simply flag every touched file with FADV_NOREUSE and let the kernel manage automatically expelling used pages. After looking deeper into the kernel implementation...
2019 Feb 11
1
[Qemu-devel] security implications of caching with virtio pmem (was Re: [PATCH v3 0/5] kvm "virtio pmem" device)
...- could be modify the applications to lock the security > relevant pages in memory. Again this becomes impractical with pmem as > host does not have visibility into that. However note that as long > as the only countermeasure linux uses is "Privileged Access" > (i.e. blocking mincore) nothing can be done as guest page cache > remains as vulnerable as host page cache. > > > Countermeasures: which host-side countermeasures can be designed would > depend on which countermeasures are used guest-side - we would need to > make sure they are not broken by pmem. Fo...
2003 Aug 22
3
PAE removal patch for testing
...a | PG_RW | PG_V | pgeflag; size -= PAGE_SIZE; tmpva += PAGE_SIZE; @@ -3009,7 +3280,9 @@ } void -pmap_unmapdev(vm_offset_t va, vm_size_t size) +pmap_unmapdev(va, size) + vm_offset_t va; + vm_size_t size; { vm_offset_t base, offset; @@ -3023,9 +3296,12 @@ * perform the pmap work for mincore */ int -pmap_mincore(pmap_t pmap, vm_offset_t addr) +pmap_mincore(pmap, addr) + pmap_t pmap; + vm_offset_t addr; { - pt_entry_t *ptep, pte; + + unsigned *ptep, pte; vm_page_t m; int val = 0; @@ -3035,7 +3311,7 @@ } if ((pte = *ptep) != 0) { - vm_paddr_t pa; + vm_offset_t pa;...
2015 Feb 07
5
[LLVMdev] mesa-10.4.4: BROKEN TLS support in GLX with llvm-toolchain v3.6.0rc2
...VE_LIBEXPAT=1 -D USE_EXTERNAL_DXTN_LIB=1 -D _GNU_SOURCE -D USE_SSE41 -D DEBUG -D USE_X86_64_ASM -D HAVE_XLOCALE_H -D HAVE_STRTOF -D HAVE_DLOPEN -D HAVE_POSIX_MEMALIGN -D HAVE_LIBDRM -D GLX_USE_DRM -D HAVE_LIBUDEV -D GLX_INDIRECT_RENDERING -D GLX_DIRECT_RENDERING -D GLX_USE_TLS -D HAVE_ALIAS -D HAVE_MINCORE -D HAVE_LLVM=0x0306 -D LLVM_VERSION_PATCH=0 -D MAPI_MODE_GLAPI -D "MAPI_ABI_HEADER=\"shared-glapi/glapi_mapi_tmp.h\"" -I . -I ../../include -I ../../src/mapi -I ../../src/mapi -I /opt/xorg/include -internal-isystem /usr/local/include -internal-isystem /opt/llvm-toolchain-3.6.0rc...
2013 Aug 21
0
Build problems: klibc with Linux 3.10.7
...UND: perf_event_open SYSCALL FOUND: io_destroy SYSCALL FOUND: prctl SYSCALL FOUND: rt_sigpending SYSCALL FOUND: rtas SYSCALL FOUND: fcntl64 SYSCALL FOUND: mq_notify SYSCALL FOUND: pwritev SYSCALL FOUND: quotactl SYSCALL FOUND: epoll_ctl SYSCALL FOUND: tuxcall SYSCALL FOUND: setresuid SYSCALL FOUND: mincore SYSCALL FOUND: rt_sigreturn SYSCALL FOUND: restart_syscall SYSCALL FOUND: process_vm_readv SYSCALL FOUND: vhangup SYSCALL FOUND: oldstat SYSCALL FOUND: query_module SYSCALL FOUND: pread64 SYSCALL FOUND: renameat SYSCALL FOUND: clock_getres SYSCALL FOUND: exit_group SYSCALL FOUND: lsetxattr SYSCALL...
2013 Aug 21
5
Build problems: klibc with Linux 3.10.7
On Tue, Aug 20, 2013 at 07:44:39AM +0200, leroy christophe wrote: > > > Find attached two patches I have in order to build klibc 2.0.2 > against kernel 3.8.13 > We had to introduce those patches when going from kernel 3.6 to kernel 3.7 > Hope it helps. > those patches are wrong and again very brittle. just use the way it is described in `make help': A) cd ~/src/linux