Re: Reserved memory for highmem bouncing (fwd)

Well, here it is. I would like to know if this makes a big difference on highmem (2GB or more) machines with heavy IO workloads. I don't have such a machine here to be able to test it. (it works with a 1GB machine, but it needs to be tested with lots of highmem to show the improvement) diff

Re: Reserved memory for highmem bouncing (fwd)

Ok. Going to write a patch and send you to test RSN. On Fri, 16 Mar 2001, Ingo Molnar wrote: > > On Thu, 15 Mar 2001, Marcelo Tosatti wrote: > > > The old create_bounce code used to set PF_MEMALLOC on the task flags > > and call wakeup_bdflush(1) in case GFP_BUFFER page allocation failed. >

Re: Reserved memory for highmem bouncing (fwd)

On Thu, 15 Mar 2001, Marcelo Tosatti wrote: > The old create_bounce code used to set PF_MEMALLOC on the task flags > and call wakeup_bdflush(1) in case GFP_BUFFER page allocation failed. > That was broken because flush_dirty_buffers() could try to flush a > buffer pointing to highmem page, which

Reserved memory for highmem bouncing (fwd)

Ingo, Any comments? -- Forwarded message -- Date: Wed, 28 Feb 2001 02:02:16 -0300 (BRT) From: Marcelo Tosatti <[EMAIL PROTECTED]> To: Ingo Molnar <[EMAIL PROTECTED]> Cc: lkml <[EMAIL PROTECTED]> Subject: Reserved memory for highmem bouncing Hi Ingo,

Reserved memory for highmem bouncing

Hi Ingo, I have a question about the highmem page IO deadlock fix which is in 2.4.2-ac. (the emergency memory thing) The old create_bounce code used to set PF_MEMALLOC on the task flags and call wakeup_bdflush(1) in case GFP_BUFFER page allocation failed. That was broken because flush_dirty_buf