Re: mm: memcontrol: rewrite uncharge API: problems

2014-07-07 Thread Johannes Weiner
On Fri, Jul 04, 2014 at 07:12:04PM -0700, Hugh Dickins wrote: > On Thu, 3 Jul 2014, Johannes Weiner wrote: > > On Thu, Jul 03, 2014 at 12:54:36PM -0700, Hugh Dickins wrote: > > > On Wed, 2 Jul 2014, Hugh Dickins wrote: > > > > On Wed, 2 Jul 2014, Johannes Weiner wrote: > > > > > > > > > > Could

Re: mm: memcontrol: rewrite uncharge API: problems

2014-07-07 Thread Johannes Weiner
On Fri, Jul 04, 2014 at 07:12:04PM -0700, Hugh Dickins wrote: On Thu, 3 Jul 2014, Johannes Weiner wrote: On Thu, Jul 03, 2014 at 12:54:36PM -0700, Hugh Dickins wrote: On Wed, 2 Jul 2014, Hugh Dickins wrote: On Wed, 2 Jul 2014, Johannes Weiner wrote: Could you give the

Re: mm: memcontrol: rewrite uncharge API: problems

2014-07-04 Thread Hugh Dickins
On Thu, 3 Jul 2014, Johannes Weiner wrote: > On Thu, Jul 03, 2014 at 12:54:36PM -0700, Hugh Dickins wrote: > > On Wed, 2 Jul 2014, Hugh Dickins wrote: > > > On Wed, 2 Jul 2014, Johannes Weiner wrote: > > > > > > > > Could you give the following patch a spin? I put it in the mmots > > > > stack

Re: mm: memcontrol: rewrite uncharge API: problems

2014-07-04 Thread Hugh Dickins
On Thu, 3 Jul 2014, Johannes Weiner wrote: On Thu, Jul 03, 2014 at 12:54:36PM -0700, Hugh Dickins wrote: On Wed, 2 Jul 2014, Hugh Dickins wrote: On Wed, 2 Jul 2014, Johannes Weiner wrote: Could you give the following patch a spin? I put it in the mmots stack on top of

Re: mm: memcontrol: rewrite uncharge API: problems

2014-07-03 Thread Johannes Weiner
On Thu, Jul 03, 2014 at 12:54:36PM -0700, Hugh Dickins wrote: > On Wed, 2 Jul 2014, Hugh Dickins wrote: > > On Wed, 2 Jul 2014, Johannes Weiner wrote: > > > > > > Could you give the following patch a spin? I put it in the mmots > > > stack on top of

Re: mm: memcontrol: rewrite uncharge API: problems

2014-07-03 Thread Hugh Dickins
On Wed, 2 Jul 2014, Hugh Dickins wrote: > On Wed, 2 Jul 2014, Johannes Weiner wrote: > > > > Could you give the following patch a spin? I put it in the mmots > > stack on top of mm-memcontrol-rewrite-charge-api-fix-shmem_unuse-fix. > > I'm just with the laptop until this evening. I slapped it

Re: mm: memcontrol: rewrite uncharge API: problems

2014-07-03 Thread Hugh Dickins
On Wed, 2 Jul 2014, Hugh Dickins wrote: On Wed, 2 Jul 2014, Johannes Weiner wrote: Could you give the following patch a spin? I put it in the mmots stack on top of mm-memcontrol-rewrite-charge-api-fix-shmem_unuse-fix. I'm just with the laptop until this evening. I slapped it on top of

Re: mm: memcontrol: rewrite uncharge API: problems

2014-07-03 Thread Johannes Weiner
On Thu, Jul 03, 2014 at 12:54:36PM -0700, Hugh Dickins wrote: On Wed, 2 Jul 2014, Hugh Dickins wrote: On Wed, 2 Jul 2014, Johannes Weiner wrote: Could you give the following patch a spin? I put it in the mmots stack on top of mm-memcontrol-rewrite-charge-api-fix-shmem_unuse-fix.

Re: mm: memcontrol: rewrite uncharge API: problems

2014-07-02 Thread Hugh Dickins
On Wed, 2 Jul 2014, Johannes Weiner wrote: > On Tue, Jul 01, 2014 at 01:46:12PM -0400, Johannes Weiner wrote: > > Hi Hugh, > > > > On Mon, Jun 30, 2014 at 04:55:10PM -0700, Hugh Dickins wrote: > > > Hi Hannes, > > > > > > Your rewrite of the memcg charge/uncharge API is bold and attractive, > >

Re: mm: memcontrol: rewrite uncharge API: problems

2014-07-02 Thread Johannes Weiner
On Tue, Jul 01, 2014 at 01:46:12PM -0400, Johannes Weiner wrote: > Hi Hugh, > > On Mon, Jun 30, 2014 at 04:55:10PM -0700, Hugh Dickins wrote: > > Hi Hannes, > > > > Your rewrite of the memcg charge/uncharge API is bold and attractive, > > but I'm having some problems with the way release_pages()

Re: mm: memcontrol: rewrite uncharge API: problems

2014-07-02 Thread Johannes Weiner
On Tue, Jul 01, 2014 at 01:46:12PM -0400, Johannes Weiner wrote: Hi Hugh, On Mon, Jun 30, 2014 at 04:55:10PM -0700, Hugh Dickins wrote: Hi Hannes, Your rewrite of the memcg charge/uncharge API is bold and attractive, but I'm having some problems with the way release_pages() now does

Re: mm: memcontrol: rewrite uncharge API: problems

2014-07-02 Thread Hugh Dickins
On Wed, 2 Jul 2014, Johannes Weiner wrote: On Tue, Jul 01, 2014 at 01:46:12PM -0400, Johannes Weiner wrote: Hi Hugh, On Mon, Jun 30, 2014 at 04:55:10PM -0700, Hugh Dickins wrote: Hi Hannes, Your rewrite of the memcg charge/uncharge API is bold and attractive, but I'm having

Re: mm: memcontrol: rewrite uncharge API: problems

2014-07-01 Thread Johannes Weiner
Hi Hugh, On Mon, Jun 30, 2014 at 04:55:10PM -0700, Hugh Dickins wrote: > Hi Hannes, > > Your rewrite of the memcg charge/uncharge API is bold and attractive, > but I'm having some problems with the way release_pages() now does > uncharging in I/O completion context. Yes, I need to make the

Re: mm: memcontrol: rewrite uncharge API: problems

2014-07-01 Thread Johannes Weiner
Hi Hugh, On Mon, Jun 30, 2014 at 04:55:10PM -0700, Hugh Dickins wrote: Hi Hannes, Your rewrite of the memcg charge/uncharge API is bold and attractive, but I'm having some problems with the way release_pages() now does uncharging in I/O completion context. Yes, I need to make the uncharge

mm: memcontrol: rewrite uncharge API: problems

2014-06-30 Thread Hugh Dickins
Hi Hannes, Your rewrite of the memcg charge/uncharge API is bold and attractive, but I'm having some problems with the way release_pages() now does uncharging in I/O completion context. At the bottom see the lockdep message I get when I start shmem swapping. Which I have not begun to attempt to

mm: memcontrol: rewrite uncharge API: problems

2014-06-30 Thread Hugh Dickins
Hi Hannes, Your rewrite of the memcg charge/uncharge API is bold and attractive, but I'm having some problems with the way release_pages() now does uncharging in I/O completion context. At the bottom see the lockdep message I get when I start shmem swapping. Which I have not begun to attempt to