All of lore.kernel.org
 help / color / mirror / Atom feed
From: Minchan Kim <minchan@kernel.org>
To: mani <manishrma@gmail.com>
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
Subject: Re: [PATCHv2 00/16] [FS, MM, block, MMC]: eMMC High Priority Interrupt Feature
Date: Mon, 14 May 2012 16:55:39 +0900	[thread overview]
Message-ID: <4FB0BA7B.1050200@kernel.org> (raw)
In-Reply-To: <CAB+TZU-r6aYn8WRZjZ0DojxMTMoc5MSx7c93W0pAad1coscPwQ@mail.gmail.com>

On 05/14/2012 04:43 PM, mani wrote:

> 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.


For example, System can have lots of order-0 pages but little order-big pages.
In this case, for getting big contiguos memory, reclaimer should write out
dirty pages while it can handle order-0 page read request.


> 
> Thanks & Regards
> Manish



-- 
Kind regards,
Minchan Kim

WARNING: multiple messages have this Message-ID (diff)
From: Minchan Kim <minchan@kernel.org>
To: mani <manishrma@gmail.com>
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
Subject: Re: [PATCHv2 00/16] [FS, MM, block, MMC]: eMMC High Priority Interrupt Feature
Date: Mon, 14 May 2012 16:55:39 +0900	[thread overview]
Message-ID: <4FB0BA7B.1050200@kernel.org> (raw)
In-Reply-To: <CAB+TZU-r6aYn8WRZjZ0DojxMTMoc5MSx7c93W0pAad1coscPwQ@mail.gmail.com>

On 05/14/2012 04:43 PM, mani wrote:

> 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.


For example, System can have lots of order-0 pages but little order-big pages.
In this case, for getting big contiguos memory, reclaimer should write out
dirty pages while it can handle order-0 page read request.


> 
> Thanks & Regards
> Manish



-- 
Kind regards,
Minchan Kim

--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2012-05-14  7:55 UTC|newest]

Thread overview: 95+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03 14:22 [PATCHv2 00/16] [FS, MM, block, MMC]: eMMC High Priority Interrupt Feature Venkatraman S
2012-05-03 14:22 ` Venkatraman S
2012-05-03 14:22 ` Venkatraman S
2012-05-03 14:23 ` [PATCH v2 01/16] FS: Added demand paging markers to filesystem Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-06 23:31   ` Dave Chinner
2012-05-06 23:31     ` Dave Chinner
2012-05-07 16:46     ` S, Venkatraman
2012-05-07 16:46       ` S, Venkatraman
2012-05-09  0:33       ` Dave Chinner
2012-05-09  0:33         ` Dave Chinner
2012-05-09  0:33         ` Dave Chinner
2012-05-09 13:59         ` Arnd Bergmann
2012-05-09 13:59           ` Arnd Bergmann
2012-05-09 15:03           ` Christoph Hellwig
2012-05-09 15:03             ` Christoph Hellwig
2012-05-09 16:54             ` Arnd Bergmann
2012-05-09 16:54               ` Arnd Bergmann
2012-05-09 15:27       ` Vivek Goyal
2012-05-09 15:27         ` Vivek Goyal
2012-05-08  6:28     ` mani
2012-05-08 16:35       ` S, Venkatraman
2012-05-08 16:35         ` S, Venkatraman
2012-05-03 14:23 ` [PATCH v2 02/16] MM: Added page swapping markers to memory management Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23 ` [PATCH v2 03/16] block: add queue attributes to manage dpmg and swapin requests Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23 ` [PATCH v2 04/16] block: add sysfs attributes for runtime control of dpmg and swapin Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23 ` [PATCH v2 05/16] block: Documentation: add sysfs ABI for expedite_dmpg and expedite_swapin Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23 ` [PATCH v2 06/16] block: treat DMPG and SWAPIN requests as special Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:38   ` Jeff Moyer
2012-05-03 14:38     ` Jeff Moyer
2012-05-03 14:38     ` Jeff Moyer
2012-05-03 16:22     ` S, Venkatraman
2012-05-03 16:22       ` S, Venkatraman
2012-05-03 14:23 ` [PATCH v2 07/16] mmc: core: helper function for finding preemptible command Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23 ` [PATCH v2 08/16] mmc: core: add preemptibility tracking fields to mmc command Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23 ` [PATCH v2 09/16] mmc: core: Add MMC abort interface Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23 ` [PATCH v2 10/16] mmc: block: Detect HPI support in card and host controller Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23 ` [PATCH v2 11/16] mmc: core: Implement foreground request preemption procedure Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23 ` [PATCH v2 12/16] mmc: sysfs: Add sysfs entry for tuning preempt_time_threshold Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23 ` [PATCH v2 13/16] mmc: Documentation: Add sysfs ABI for hpi_time_threshold Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23 ` [PATCH v2 14/16] mmc: block: Implement HPI invocation and handling logic Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-09  8:35   ` kdorfman
2012-05-09  8:35     ` kdorfman
2012-05-09  8:35     ` kdorfman
2012-05-09  8:35     ` kdorfman
2012-05-09 14:01     ` Arnd Bergmann
2012-05-09 14:01       ` Arnd Bergmann
2012-05-09 14:06     ` S, Venkatraman
2012-05-09 14:06       ` S, Venkatraman
2012-05-03 14:23 ` [PATCH v2 15/16] mmc: Update preempted request with CORRECTLY_PRG_SECTORS_NUM info Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23 ` [PATCH v2 16/16] mmc: omap_hsmmc: Implement abort_req host_ops Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-03 14:23   ` Venkatraman S
2012-05-08  7:46 ` [PATCHv2 00/16] [FS, MM, block, MMC]: eMMC High Priority Interrupt Feature Minchan Kim
2012-05-08  7:46   ` Minchan Kim
2012-05-08 16:31   ` S, Venkatraman
2012-05-08 16:31     ` S, Venkatraman
2012-05-09  0:45     ` Minchan Kim
2012-05-09  0:45       ` Minchan Kim
2012-05-11 19:18       ` S, Venkatraman
2012-05-11 19:18         ` S, Venkatraman
2012-05-11 19:18         ` S, Venkatraman
2012-05-14  7:43       ` mani
2012-05-14  7:53         ` mani
2012-05-14  7:55         ` Minchan Kim [this message]
2012-05-14  7:55           ` Minchan Kim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FB0BA7B.1050200@kernel.org \
    --to=minchan@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=manishrma@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.