similar to: Clearing out or reclaiming memory

Check the page refcount rather than the type count when deciding if a page is still mapped. This catches pages which are mapped by qemu; it also removes the need for gnttab_is_granted(). Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

On 1/3/19 6:37 AM, Richard W.M. Jones wrote: > The original plan was to have a background thread doing the reclaim. > However that cannot work given the design of filters, because a > background thread cannot access the next_ops struct which is only > available during requests. > > Therefore we spread the work over the request threads. Each blk_* > function checks whether

The following is mainly a capture of parts of multiple off-line discussions within members of the Crossbow team (Gopi, Thiru, Roamer, May-Lin, Thirumailai, Nitin, KB, ...), I thought I''d open it up to other participants. Crossbow''s core scheduling involves switching a NIC (or individual Rx rings on the NIC) to polling mode. The receive interrupt will become not only rarer,

Dear list, I am trying to reclaim what I think is lost memory in R, I have been using gc(), rm() and also using Rprof to figure out where all the memory is going but I might be missing something. I have the following situation basic loop which calls memoryHogFunction: for i in (1:N) { dataset <- generateDataset(i) fit <- try( memoryHogFunction(dataset, otherParameters)) } and

On 1/1/19 8:33 AM, Richard W.M. Jones wrote: > The original plan was to have a background thread doing the reclaim. > However that cannot work given the design of filters, because a > background thread cannot access the next_ops struct which is only > available during requests. > > Therefore we spread the work over the request threads. Each blk_* > function checks whether

The original plan was to have a background thread doing the reclaim. However that cannot work given the design of filters, because a background thread cannot access the next_ops struct which is only available during requests. Therefore we spread the work over the request threads. Each blk_* function checks whether there is work to do, and if there is will reclaim up to two blocks from the cache

The original plan was to have a background thread doing the reclaim. However that cannot work given the design of filters, because a background thread cannot access the next_ops struct which is only available during requests. Therefore we spread the work over the request threads. Each blk_* function checks whether there is work to do, and if there is will reclaim up to two blocks from the cache

Hello, First of all, I'm new to R and I don't have anyone who already knows the language to ask for tips, so please excuse my ignorance. I'm trying to download data direct from the Federal Reserve statistics website and graph it, using the following: #This downloads the data from the Fed website

The original plan was to have a background thread doing the reclaim. However that cannot work given the design of filters, because a background thread cannot access the next_ops struct which is only available during requests. Therefore we spread the work over the request threads. Each blk_* function checks whether there is work to do, and if there is will reclaim up to two blocks from the cache

When trying to do a yum update, I am told I need more space in /boot. When I check the contents of /boot (ls -l /boot), there are no files. If I do a df -h, there is no available space yet it shows that it has a lot of used space. The fstab shows the following: # This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/VolGroup00/LogVol00 /

The original plan was to have a background thread doing the reclaim. However that cannot work given the design of filters, because a background thread cannot access the next_ops struct which is only available during requests. Therefore we spread the work over the request threads. Each blk_* function checks whether there is work to do, and if there is will reclaim up to two blocks from the cache

Patch 1 is the same as last time, except for a minor comment fix. Patch 2 should address everything that Eric mentioned in his review, and has been retested. Rich.

Hi All, In another thread Andy Liaw, who CRAN lists as locfit maintainer; said: <quote> From: "Liaw, Andy" <andy_liaw at merck.com> To: "Guy Green" <guygreen at netvigator.com>; <r-help at r-project.org> Subject: Re: Alternatives to linear regression with multiple variables Date: 22 February 2010 17:50 You can try the locfit package, which I believe

Hello, I am trying to create a graphic to help me visualise data. A (very simplified) sample of the data is http://n4.nabble.com/file/n1839676/circle_data.txt circle_data.txt : Aug-07 Nov-07 Feb-08 data1 1 1.5 -1 data2 1 1.2 1.6 data3 1.3 1.4 1.8 data4 1.3

This patch series enhances the cache filter in a few ways, primarily adding a "cache-on-read" feature (similar to qemu's copyonread); and adding the ability to limit the cache size and the antecedent of that which is having a method to reclaim cache blocks. As the cache is stored as a sparse temporary file, reclaiming cache blocks simply means punching holes in the temporary file.

The original plan was to have a background thread doing the reclaim. However that cannot work given the design of filters, because a background thread cannot access the next_ops struct which is only available during requests. Therefore we spread the work over the request threads. Each blk_* function checks whether there is work to do, and if there is will reclaim up to two blocks from the cache

v4: https://www.redhat.com/archives/libguestfs/2019-January/msg00032.html v5: - Now we set the block size at run time. I'd like to say that I was able to test this change, but unfortunately I couldn't find any easy way to create a filesystem on x86-64 with a block size > 4K. Ext4 doesn't support it at all, and XFS doesn't support block size > page size (and I

Dear all, I am using R 2.1.0 for Windows on XP SP2. In a loop such as below, we can track the progress by a screen print display as below (in S): for (i in 1:10){ print(paste("Starting simulation run no...",i)) result<-c(result,mean(data)) #A dummy example of the simulation to be done } In S-plus environment, the statements Starting simulation run no...1 Starting simulation

Are there commands that can do more complete clean-up than "rm(list=ls(all=T))"? My understanding is that one only clears the variables... not functions/packages, etc... Thanks a lot! [[alternative HTML version deleted]]

Hello all, I am interested in using BackgrounDRb to clear out ActiveRecord based sessions. I have this working, just with a small hitch, here is the code: class ClearSessionsWorker < BackgrounDRb::Rails repeat_every 7.minutes first_run Time.now def do_work(args) Session.destroy_all(["updated_at < ?", 20.minute.ago ]) end end It''s not very complicated and