On Sun, May 10, 2015 at 01:34:29PM +0300, Vladimir Davydov wrote:
> On Sun, May 10, 2015 at 12:12:38AM +0900, Minchan Kim wrote:
> > Yeb, I might be paranoid but my point is it might work now on most of
> > arch but it seem to be buggy/fragile/subtle because we couldn't prove
> > all arch/compiler
On Sun, May 10, 2015 at 01:34:29PM +0300, Vladimir Davydov wrote:
On Sun, May 10, 2015 at 12:12:38AM +0900, Minchan Kim wrote:
Yeb, I might be paranoid but my point is it might work now on most of
arch but it seem to be buggy/fragile/subtle because we couldn't prove
all arch/compiler don't
On Sun, May 10, 2015 at 12:12:38AM +0900, Minchan Kim wrote:
> On Fri, May 08, 2015 at 12:56:04PM +0300, Vladimir Davydov wrote:
> > On Mon, May 04, 2015 at 07:54:59PM +0900, Minchan Kim wrote:
> > > So, I guess once below compiler optimization happens in
> > > __page_set_anon_rmap,
> > > it
On Sun, May 10, 2015 at 12:12:38AM +0900, Minchan Kim wrote:
On Fri, May 08, 2015 at 12:56:04PM +0300, Vladimir Davydov wrote:
On Mon, May 04, 2015 at 07:54:59PM +0900, Minchan Kim wrote:
So, I guess once below compiler optimization happens in
__page_set_anon_rmap,
it could be corrupt
Hello, Vladimir
On Fri, May 08, 2015 at 12:56:04PM +0300, Vladimir Davydov wrote:
> On Mon, May 04, 2015 at 07:54:59PM +0900, Minchan Kim wrote:
> > So, I guess once below compiler optimization happens in
> > __page_set_anon_rmap,
> > it could be corrupt in page_refernced.
> >
> >
Hello, Vladimir
On Fri, May 08, 2015 at 12:56:04PM +0300, Vladimir Davydov wrote:
On Mon, May 04, 2015 at 07:54:59PM +0900, Minchan Kim wrote:
So, I guess once below compiler optimization happens in
__page_set_anon_rmap,
it could be corrupt in page_refernced.
__page_set_anon_rmap:
On Mon, May 04, 2015 at 07:54:59PM +0900, Minchan Kim wrote:
> So, I guess once below compiler optimization happens in __page_set_anon_rmap,
> it could be corrupt in page_refernced.
>
> __page_set_anon_rmap:
> page->mapping = (struct address_space *) anon_vma;
> page->mapping =
On Mon, May 04, 2015 at 07:54:59PM +0900, Minchan Kim wrote:
So, I guess once below compiler optimization happens in __page_set_anon_rmap,
it could be corrupt in page_refernced.
__page_set_anon_rmap:
page-mapping = (struct address_space *) anon_vma;
page-mapping = (struct
On Mon, May 04, 2015 at 12:49:39PM +0300, Vladimir Davydov wrote:
> On Mon, May 04, 2015 at 12:17:22PM +0900, Minchan Kim wrote:
> > On Thu, Apr 30, 2015 at 05:50:55PM +0300, Vladimir Davydov wrote:
> > > On Thu, Apr 30, 2015 at 05:25:31PM +0900, Minchan Kim wrote:
> > > > On Wed, Apr 29, 2015 at
On Mon, May 04, 2015 at 12:17:22PM +0900, Minchan Kim wrote:
> On Thu, Apr 30, 2015 at 05:50:55PM +0300, Vladimir Davydov wrote:
> > On Thu, Apr 30, 2015 at 05:25:31PM +0900, Minchan Kim wrote:
> > > On Wed, Apr 29, 2015 at 12:12:48PM +0300, Vladimir Davydov wrote:
> > > > On Wed, Apr 29, 2015 at
On Mon, May 04, 2015 at 12:17:22PM +0900, Minchan Kim wrote:
On Thu, Apr 30, 2015 at 05:50:55PM +0300, Vladimir Davydov wrote:
On Thu, Apr 30, 2015 at 05:25:31PM +0900, Minchan Kim wrote:
On Wed, Apr 29, 2015 at 12:12:48PM +0300, Vladimir Davydov wrote:
On Wed, Apr 29, 2015 at 01:35:36PM
On Mon, May 04, 2015 at 12:49:39PM +0300, Vladimir Davydov wrote:
On Mon, May 04, 2015 at 12:17:22PM +0900, Minchan Kim wrote:
On Thu, Apr 30, 2015 at 05:50:55PM +0300, Vladimir Davydov wrote:
On Thu, Apr 30, 2015 at 05:25:31PM +0900, Minchan Kim wrote:
On Wed, Apr 29, 2015 at 12:12:48PM
On Thu, Apr 30, 2015 at 05:50:55PM +0300, Vladimir Davydov wrote:
> On Thu, Apr 30, 2015 at 05:25:31PM +0900, Minchan Kim wrote:
> > On Wed, Apr 29, 2015 at 12:12:48PM +0300, Vladimir Davydov wrote:
> > > On Wed, Apr 29, 2015 at 01:35:36PM +0900, Minchan Kim wrote:
> > > > On Tue, Apr 28, 2015 at
On Thu, Apr 30, 2015 at 05:50:55PM +0300, Vladimir Davydov wrote:
On Thu, Apr 30, 2015 at 05:25:31PM +0900, Minchan Kim wrote:
On Wed, Apr 29, 2015 at 12:12:48PM +0300, Vladimir Davydov wrote:
On Wed, Apr 29, 2015 at 01:35:36PM +0900, Minchan Kim wrote:
On Tue, Apr 28, 2015 at 03:24:42PM
On Thu, Apr 30, 2015 at 05:25:31PM +0900, Minchan Kim wrote:
> On Wed, Apr 29, 2015 at 12:12:48PM +0300, Vladimir Davydov wrote:
> > On Wed, Apr 29, 2015 at 01:35:36PM +0900, Minchan Kim wrote:
> > > On Tue, Apr 28, 2015 at 03:24:42PM +0300, Vladimir Davydov wrote:
> > > > +#ifdef
On Wed, Apr 29, 2015 at 12:12:48PM +0300, Vladimir Davydov wrote:
> On Wed, Apr 29, 2015 at 01:35:36PM +0900, Minchan Kim wrote:
> > On Tue, Apr 28, 2015 at 03:24:42PM +0300, Vladimir Davydov wrote:
> > > diff --git a/fs/proc/page.c b/fs/proc/page.c
> > > index 70d23245dd43..cfc55ba7fee6 100644
>
Hi,
On Wed, Apr 29, 2015 at 11:31:49AM +0300, Vladimir Davydov wrote:
> On Wed, Apr 29, 2015 at 01:57:59PM +0900, Minchan Kim wrote:
> > On Tue, Apr 28, 2015 at 03:24:42PM +0300, Vladimir Davydov wrote:
> > > @@ -69,6 +69,14 @@ There are four components to pagemap:
> > > memory cgroup each
Hi,
On Wed, Apr 29, 2015 at 11:31:49AM +0300, Vladimir Davydov wrote:
On Wed, Apr 29, 2015 at 01:57:59PM +0900, Minchan Kim wrote:
On Tue, Apr 28, 2015 at 03:24:42PM +0300, Vladimir Davydov wrote:
@@ -69,6 +69,14 @@ There are four components to pagemap:
memory cgroup each page is
On Wed, Apr 29, 2015 at 12:12:48PM +0300, Vladimir Davydov wrote:
On Wed, Apr 29, 2015 at 01:35:36PM +0900, Minchan Kim wrote:
On Tue, Apr 28, 2015 at 03:24:42PM +0300, Vladimir Davydov wrote:
diff --git a/fs/proc/page.c b/fs/proc/page.c
index 70d23245dd43..cfc55ba7fee6 100644
---
On Thu, Apr 30, 2015 at 05:25:31PM +0900, Minchan Kim wrote:
On Wed, Apr 29, 2015 at 12:12:48PM +0300, Vladimir Davydov wrote:
On Wed, Apr 29, 2015 at 01:35:36PM +0900, Minchan Kim wrote:
On Tue, Apr 28, 2015 at 03:24:42PM +0300, Vladimir Davydov wrote:
+#ifdef CONFIG_IDLE_PAGE_TRACKING
On Wed, Apr 29, 2015 at 01:35:36PM +0900, Minchan Kim wrote:
> On Tue, Apr 28, 2015 at 03:24:42PM +0300, Vladimir Davydov wrote:
> > diff --git a/fs/proc/page.c b/fs/proc/page.c
> > index 70d23245dd43..cfc55ba7fee6 100644
> > --- a/fs/proc/page.c
> > +++ b/fs/proc/page.c
> > @@ -275,6 +275,156 @@
On Wed, Apr 29, 2015 at 01:57:59PM +0900, Minchan Kim wrote:
> On Tue, Apr 28, 2015 at 03:24:42PM +0300, Vladimir Davydov wrote:
> > @@ -69,6 +69,14 @@ There are four components to pagemap:
> > memory cgroup each page is charged to, indexed by PFN. Only available
> > when
> > CONFIG_MEMCG
On Wed, Apr 29, 2015 at 01:57:59PM +0900, Minchan Kim wrote:
On Tue, Apr 28, 2015 at 03:24:42PM +0300, Vladimir Davydov wrote:
@@ -69,6 +69,14 @@ There are four components to pagemap:
memory cgroup each page is charged to, indexed by PFN. Only available
when
CONFIG_MEMCG is set.
On Wed, Apr 29, 2015 at 01:35:36PM +0900, Minchan Kim wrote:
On Tue, Apr 28, 2015 at 03:24:42PM +0300, Vladimir Davydov wrote:
diff --git a/fs/proc/page.c b/fs/proc/page.c
index 70d23245dd43..cfc55ba7fee6 100644
--- a/fs/proc/page.c
+++ b/fs/proc/page.c
@@ -275,6 +275,156 @@ static
On Tue, Apr 28, 2015 at 03:24:42PM +0300, Vladimir Davydov wrote:
> Knowing the portion of memory that is not used by a certain application
> or memory cgroup (idle memory) can be useful for partitioning the system
> efficiently, e.g. by setting memory cgroup limits appropriately.
> Currently, the
On Tue, Apr 28, 2015 at 03:24:42PM +0300, Vladimir Davydov wrote:
> Knowing the portion of memory that is not used by a certain application
> or memory cgroup (idle memory) can be useful for partitioning the system
> efficiently, e.g. by setting memory cgroup limits appropriately.
> Currently, the
Knowing the portion of memory that is not used by a certain application
or memory cgroup (idle memory) can be useful for partitioning the system
efficiently, e.g. by setting memory cgroup limits appropriately.
Currently, the only means to estimate the amount of idle memory provided
by the kernel
Knowing the portion of memory that is not used by a certain application
or memory cgroup (idle memory) can be useful for partitioning the system
efficiently, e.g. by setting memory cgroup limits appropriately.
Currently, the only means to estimate the amount of idle memory provided
by the kernel
On Tue, Apr 28, 2015 at 03:24:42PM +0300, Vladimir Davydov wrote:
Knowing the portion of memory that is not used by a certain application
or memory cgroup (idle memory) can be useful for partitioning the system
efficiently, e.g. by setting memory cgroup limits appropriately.
Currently, the
On Tue, Apr 28, 2015 at 03:24:42PM +0300, Vladimir Davydov wrote:
Knowing the portion of memory that is not used by a certain application
or memory cgroup (idle memory) can be useful for partitioning the system
efficiently, e.g. by setting memory cgroup limits appropriately.
Currently, the
30 matches
Mail list logo