From mboxrd@z Thu Jan 1 00:00:00 1970 From: mani Subject: Re: [PATCHv2 00/16] [FS, MM, block, MMC]: eMMC High Priority Interrupt Feature Date: Mon, 14 May 2012 13:13:07 +0530 Message-ID: References: <1336054995-22988-1-git-send-email-svenkatr@ti.com> <4FA8CF5E.1070202@kernel.org> <4FA9BE10.1030007@kernel.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=20cf307cfe7aebe59904bffa3d26 Cc: linux-mmc@vger.kernel.org, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org To: Minchan Kim Return-path: In-Reply-To: <4FA9BE10.1030007@kernel.org> Sender: owner-linux-mm@kvack.org List-Id: linux-fsdevel.vger.kernel.org --20cf307cfe7aebe59904bffa3d26 Content-Type: text/plain; charset=ISO-8859-1 Dear Kim, I have a query here .. > > My point is that it would be better for read to not preempt > write-for-page_reclaim. > And we can identify it by PG_reclaim. You can get the idea. > > I think If there is no page available then no read will proceed. When read request comes it reclaim the pages (starts the write if syncable pages ) and get back after reclaiming the pages. Only then a read request will come to the MMC subsystem. And i think the reclaim algorithm will reclaim some substantial amount of pages at a time instead of a single page. So if we get few pages during the reclamation so there will be no problem in halting the another write ops for proceeding the reads ? Can we think of a scenario when we are reclaiming the pages and write ops is going on where as a high priority read for the interrupt handler is pending ? Please correct me if i am wrong. Thanks & Regards Manish --20cf307cfe7aebe59904bffa3d26 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Dear Kim,

I have a query here ..

My point is that it would be better for read to not preempt write-for= -page_reclaim.
And we can identify it by PG_reclaim. You can get the idea.

I think If there is no page available then no read w= ill proceed.
When read request comes it reclaim the pages (starts the w= rite if syncable pages ) and get back after reclaiming the pages.
Only then a read request will come to the MMC subsystem.
And i think th= e reclaim algorithm will reclaim some substantial amount of pages at a time= instead of a single page.
So if we get few pages during the reclamatio= n so there will be no problem in halting the another write ops for proceedi= ng the reads ?

Can we think of a scenario when we are reclaiming the pages and write o= ps is going on where as a high priority read for the interrupt handler is p= ending ?

Please correct me if i am wrong.

Thanks & Regard= s
Manish
--20cf307cfe7aebe59904bffa3d26-- -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org