From: Alasdair G Kergon <agk@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: axboe@kernel.dk, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
dm-devel <dm-devel@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: Queue upcall locking (was: [RFC][PATCH] fix dm_any_congested() to properly sync up with suspend code path)
Date: Mon, 10 Nov 2008 14:35:22 +0000 [thread overview]
Message-ID: <20081110143522.GE16649@agk.fab.redhat.com> (raw)
In-Reply-To: <1226327210.7685.173.camel@twins>
On Mon, Nov 10, 2008 at 03:26:50PM +0100, Peter Zijlstra wrote:
> Fix the infrastructure by adding a function call so that you can have
> the individual devices report their congestion state to the aggregate.
Which requires knowing/accessing some device hierarchy, which would be nice
for other things too (like propagation of notification of changes to device
properties such as size, hardsect size etc.).
Alasdair
--
agk@redhat.com
WARNING: multiple messages have this Message-ID (diff)
From: Alasdair G Kergon <agk@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Mikulas Patocka <mpatocka@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Chandra Seetharaman <sekharan@us.ibm.com>,
dm-devel <dm-devel@redhat.com>,
linux-kernel@vger.kernel.org, axboe@kernel.dk
Subject: Re: Queue upcall locking (was: [dm-devel] [RFC][PATCH] fix dm_any_congested() to properly sync up with suspend code path)
Date: Mon, 10 Nov 2008 14:35:22 +0000 [thread overview]
Message-ID: <20081110143522.GE16649@agk.fab.redhat.com> (raw)
In-Reply-To: <1226327210.7685.173.camel@twins>
On Mon, Nov 10, 2008 at 03:26:50PM +0100, Peter Zijlstra wrote:
> Fix the infrastructure by adding a function call so that you can have
> the individual devices report their congestion state to the aggregate.
Which requires knowing/accessing some device hierarchy, which would be nice
for other things too (like propagation of notification of changes to device
properties such as size, hardsect size etc.).
Alasdair
--
agk@redhat.com
next prev parent reply other threads:[~2008-11-10 14:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 4:00 [RFC][PATCH] fix dm_any_congested() to properly sync up with suspend code path Chandra Seetharaman
2008-11-10 13:11 ` Queue upcall locking (was: [RFC][PATCH] fix dm_any_congested() to properly sync up with suspend code path) Mikulas Patocka
2008-11-10 13:11 ` Queue upcall locking (was: [dm-devel] " Mikulas Patocka
2008-11-10 13:54 ` Queue upcall locking (was: " Christoph Hellwig
2008-11-10 13:54 ` Queue upcall locking (was: [dm-devel] " Christoph Hellwig
2008-11-10 14:19 ` Queue upcall locking (was: " Mikulas Patocka
2008-11-10 14:19 ` Queue upcall locking (was: [dm-devel] " Mikulas Patocka
2008-11-10 14:26 ` Peter Zijlstra
2008-11-10 14:32 ` Queue upcall locking (was: " Mikulas Patocka
2008-11-10 14:32 ` Queue upcall locking (was: [dm-devel] " Mikulas Patocka
2008-11-10 14:46 ` Peter Zijlstra
2008-11-10 14:55 ` Queue upcall locking (was: " Mikulas Patocka
2008-11-10 14:55 ` Queue upcall locking (was: [dm-devel] " Mikulas Patocka
2008-11-10 14:35 ` Alasdair G Kergon [this message]
2008-11-10 14:35 ` Alasdair G Kergon
2008-11-11 18:18 ` Queue upcall locking (was: " Christoph Hellwig
2008-11-11 18:18 ` Queue upcall locking (was: [dm-devel] " Christoph Hellwig
2008-11-11 22:08 ` Queue upcall locking (was: " Mikulas Patocka
2008-11-11 22:08 ` Queue upcall locking (was: [dm-devel] " Mikulas Patocka
2008-11-10 14:27 ` Queue upcall locking (was: " Alasdair G Kergon
2008-11-10 14:27 ` Queue upcall locking (was: [dm-devel] " Alasdair G Kergon
2008-11-10 14:40 ` Queue upcall locking (was: " Mikulas Patocka
2008-11-10 14:40 ` Queue upcall locking (was: [dm-devel] " Mikulas Patocka
2008-11-11 18:22 ` Christoph Hellwig
2008-11-11 18:21 ` Christoph Hellwig
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=20081110143522.GE16649@agk.fab.redhat.com \
--to=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=peterz@infradead.org \
/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.