Date: Thu, 6 Dec 2007 16:29:15 -0800
From: Andrew Morton <akpm@linux-foundation.org>
To: Daniel Phillips <phillips@phunq.net>
Cc: davidsen@tmr.com, linux-kernel@vger.kernel.org, peterz@infradead.org
Subject: Re: [RFC] [PATCH] A clean approach to writeout throttling
Message-Id: <20071206162915.a3917d1c.akpm@linux-foundation.org>
In-Reply-To: <200712061604.41490.phillips@phunq.net>
References: <200712051603.02183.phillips@phunq.net>
	<200712052221.45409.phillips@phunq.net>
	<47586F59.5090507@tmr.com>
	<200712061604.41490.phillips@phunq.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 886
Lines: 31

On Thu, 6 Dec 2007 16:04:41 -0800
Daniel Phillips <phillips@phunq.net> wrote:

> The runner up key idea is that we will gain a notion of "block device 
> stack" (or block stack for short, so that we may implement block 
> stackers) which for the time being will simply be Device Mapper's 
> notion of device stack, however many warts that may have.  It's there 
> now and we use it for ddsnap.

Perhaps all we need to track is the outermost point?

submit_bio(...)
{
	bool remove_the_rq = false;

	...
	if (current->the_rq == NULL) {
		current->the_rq = rq;
		remove_the_rq = true;
	}
	...
	if (remove_the_rq)
		current->the_rq = NULL;
}

?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/