linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Ming Lei <ming.lei@canonical.com>
Cc: linux-kernel@vger.kernel.org, Oliver Neukum <oneukum@suse.de>,
	Minchan Kim <minchan@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>, Jens Axboe <axboe@kernel.dk>,
	"David S. Miller" <davem@davemloft.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	netdev@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-pm@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC PATCH v2 2/6] PM / Runtime: introduce pm_runtime_set_memalloc_noio()
Date: Mon, 22 Oct 2012 10:33:13 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44L0.1210221023300.1724-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <1350894794-1494-3-git-send-email-ming.lei@canonical.com>

On Mon, 22 Oct 2012, Ming Lei wrote:

> +void pm_runtime_set_memalloc_noio(struct device *dev, bool enable)
> +{
> +	dev->power.memalloc_noio_resume = enable;
> +
> +	if (!dev->parent)
> +		return;
> +
> +	if (enable) {
> +		pm_runtime_set_memalloc_noio(dev->parent, 1);
> +	} else {
> +		/* only clear the flag for one device if all
> +		 * children of the device don't set the flag.
> +		 */
> +		if (device_for_each_child(dev->parent, NULL,
> +					  dev_memalloc_noio))
> +			return;
> +
> +		pm_runtime_set_memalloc_noio(dev->parent, 0);
> +	}
> +}
> +EXPORT_SYMBOL_GPL(pm_runtime_set_memalloc_noio);

Tail recursion should be implemented as a loop, not as an explicit
recursion.  That is, the function should be:

void pm_runtime_set_memalloc_noio(struct device *dev, bool enable)
{
	do {
		dev->power.memalloc_noio_resume = enable;

		if (!enable) {
			/*
			 * Don't clear the parent's flag if any of the
			 * parent's children have their flag set.
			 */
			if (device_for_each_child(dev->parent, NULL,
					  dev_memalloc_noio))
				return;
		}
		dev = dev->parent;
	} while (dev);
}

except that you need to add locking, for two reasons:

	There's a race.  What happens if another child sets the flag
	between the time device_for_each_child() runs and the next loop
	iteration?

	Even without a race, access to bitfields is not SMP-safe 
	without locking.

Alan Stern

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

  reply	other threads:[~2012-10-22 14:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22  8:33 [RFC PATCH v2 0/6] solve deadlock caused by memory allocation with I/O Ming Lei
2012-10-22  8:33 ` [RFC PATCH v2 1/6] mm: teach mm by current context info to not do I/O during memory allocation Ming Lei
2012-10-22  8:33 ` [RFC PATCH v2 2/6] PM / Runtime: introduce pm_runtime_set_memalloc_noio() Ming Lei
2012-10-22 14:33   ` Alan Stern [this message]
2012-10-23  9:08     ` Ming Lei
2012-10-23 14:46       ` Alan Stern
2012-10-23 15:18         ` Ming Lei
2012-10-23 18:16           ` Alan Stern
2012-10-24  9:06           ` David Laight
2012-10-24 12:26             ` Alan Cox
2012-10-22  8:33 ` [RFC PATCH v2 3/6] block/genhd.c: apply pm_runtime_set_memalloc_noio on block devices Ming Lei
2012-10-22  8:33 ` [RFC PATCH v2 4/6] net/core: apply pm_runtime_set_memalloc_noio on network devices Ming Lei
2012-10-22 19:18   ` Alan Stern
2012-10-23  8:42     ` Ming Lei
2012-10-22  8:33 ` [RFC PATCH v2 5/6] PM / Runtime: force memory allocation with no I/O during runtime_resume callbcack Ming Lei
2012-10-22  8:33 ` [RFC PATCH v2 6/6] USB: forbid memory allocation with I/O during bus reset Ming Lei
2012-10-22 14:37   ` Alan Stern
2012-10-23  8:44     ` Ming Lei

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=Pine.LNX.4.44L0.1210221023300.1724-100000@iolanthe.rowland.org \
    --to=stern@rowland.harvard.edu \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=minchan@kernel.org \
    --cc=ming.lei@canonical.com \
    --cc=netdev@vger.kernel.org \
    --cc=oneukum@suse.de \
    --cc=rjw@sisk.pl \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox