search for: freeable

...(path+i) == '/' && j>0 && *(path+j-1) == '/') > j--; > > *(path+j) = *(path+i); > j++; > } > return real_path; > } > /* Takes a path from jail perspective and converts it to the actual path. This function frees path (so expects a freeable pointer) or reuses it so in any case returns a freeable pointer. */ > static char* jail_to_actual(char* path) { > if (jail == NULL) return path; > char* shortened = shorten_path(path); > char* translated = concat_path(jail,shortened); > free(shortened); > return translated; &...

Hi, Please forgive me if my searching-fu has failed me in this case, but I''ve been unable to find any information on how people are going about monitoring and alerting regarding memory usage on Solaris hosts using ZFS. The problem is not that the ZFS ARC is using up the memory, but that the script Nagios is using to check memory usage simply sees, say 96% RAM used, and alerts. The

...as a way to dynamically right-size the balloon. Two reasons I didn't go with the above implementation: 1. I need to support guests before Linux 4.19 which don't have the shrinker behavior. 2. Memory in the balloon does not appear as "available" in /proc/meminfo even though it is freeable. This is confusing to users, but isn't a deal breaker. If we added a DEFLATE_ON_PRESSURE feature bit that indicated shrinker API support then that would resolve reason #1 (ideally we would backport the bit to 4.19). In any case, the shrinker behavior when pressuring page cache is more of an i...

...as a way to dynamically right-size the balloon. Two reasons I didn't go with the above implementation: 1. I need to support guests before Linux 4.19 which don't have the shrinker behavior. 2. Memory in the balloon does not appear as "available" in /proc/meminfo even though it is freeable. This is confusing to users, but isn't a deal breaker. If we added a DEFLATE_ON_PRESSURE feature bit that indicated shrinker API support then that would resolve reason #1 (ideally we would backport the bit to 4.19). In any case, the shrinker behavior when pressuring page cache is more of an i...

> On 12/08/2016 08:45 PM, Li, Liang Z wrote: > > What's the conclusion of your discussion? It seems you want some > > statistic before deciding whether to ripping the bitmap from the ABI, > > am I right? > > I think Andrea and David feel pretty strongly that we should remove the > bitmap, unless we have some data to support keeping it. I don't feel as >

> On 12/08/2016 08:45 PM, Li, Liang Z wrote: > > What's the conclusion of your discussion? It seems you want some > > statistic before deciding whether to ripping the bitmap from the ABI, > > am I right? > > I think Andrea and David feel pretty strongly that we should remove the > bitmap, unless we have some data to support keeping it. I don't feel as >

...s at zero -- unless a new claim is subsequently staked. See Note 2. The systemwide variable total_unclaimed_pages is always the sum of d->unclaimed_pages, across all domains. A non-domain- specific heap allocation will fail if total_unclaimed_pages exceeds free (plus, on tmem enabled systems, freeable) pages. Claim semantics may be modified by flags. The initial implementation has one flag, which discerns whether the caller would like tmem freeable pages to be considered in determining whether or not the claim can be successfully staked. Future flags may, for example, specify that the caller w...

...;, "[<Domain>|-a] [-u[=UUID] [-A[=AUTH]", " -a Authenticate for all tmem pools\n" @@ -367,12 +367,12 @@ struct cmd_spec cmd_table[] = { " -A AUTH 0=auth,1=deauth", }, { "tmem-freeable", - &main_tmem_freeable, 0, + &main_tmem_freeable, 0, 0, "Get information about how much freeable memory (MB) is in-use by tmem", "", }, { "cpupool-create", - &main_cpupoolcreate, 1, + &main_cpupoolcreate...

...our implementation do? > Two reasons I didn't go with the above implementation: > 1. I need to support guests before Linux 4.19 which don't have the shrinker > behavior. > 2. Memory in the balloon does not appear as "available" in /proc/meminfo even > though it is freeable. This is confusing to users, but isn't a deal breaker. > > If we added a DEFLATE_ON_PRESSURE feature bit that indicated shrinker API > support then that would resolve reason??#1 (ideally we would backport the bit to > 4.19). We could declare lack of pagecache pressure with DEFLATE...

...sed optionally on THP backed guests. This option with THP guests would allow a highlevel management software to provide a "don't reduce guest performance" while shrinking the memory size of the guest from the GUI. If you deselect the option, you can shrink down to the last freeable 4k guest page, but doing so may have to split THP in the host (you don't know for sure if they were really THP but they could have been), and it may regress performance. Inflating the balloon while passing a minimum granularity "order" of the pages being zapped, will guara...

...Two reasons I didn't go with the above implementation: > > 1. I need to support guests before Linux 4.19 which don't have the > shrinker > > behavior. > > 2. Memory in the balloon does not appear as "available" in /proc/meminfo > even > > though it is freeable. This is confusing to users, but isn't a deal > breaker. > > > > If we added a DEFLATE_ON_PRESSURE feature bit that indicated shrinker API > > support then that would resolve reason #1 (ideally we would backport the > bit to > > 4.19). > > We could declare la...

On Tue, Feb 4, 2020 at 12:29 AM David Hildenbrand <david at redhat.com> wrote: > On 03.02.20 21:32, Tyler Sanderson wrote: > > There were apparently good reasons for moving away from OOM notifier > > callback: > > https://lkml.org/lkml/2018/7/12/314 > > https://lkml.org/lkml/2018/8/2/322 > > > > In particular the OOM notifier is worse than the shrinker

On Tue, Feb 4, 2020 at 12:29 AM David Hildenbrand <david at redhat.com> wrote: > On 03.02.20 21:32, Tyler Sanderson wrote: > > There were apparently good reasons for moving away from OOM notifier > > callback: > > https://lkml.org/lkml/2018/7/12/314 > > https://lkml.org/lkml/2018/8/2/322 > > > > In particular the OOM notifier is worse than the shrinker

We have a reproducible problem with FreeBSD-4.7 which is apparently a deadlock. The system is undergoing a filesystem stress test. The machine is pingable, but console and most other features are unresponsive. The console debugger can be accessed. The following information is available with db's "ps". I suspect the wchan of "inode" to be what everything is waiting on.

This is v3 of my disk series. What were previously patches 01-06 have been applied. These are the tested and updated remainder, addressing the previous comments. 1 Preparatory work. 2-4 The new parser and its documentation. 5-6 Replace old parsers with calls to the new one. 7-8 Two features, one of them essential. 9 Basic test suite for disk string parsing, as adhoc script.