From: Daniel Phillips <phillips@phunq.net>
To: "Mike Snitzer" <snitzer@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] ddtree: A git kernel tree for storage servers
Date: Wed, 19 Mar 2008 15:33:19 -0800 [thread overview]
Message-ID: <200803191633.20922.phillips@phunq.net> (raw)
In-Reply-To: <170fa0d20803191323o65bd9738j80511de2c9f6a03c@mail.gmail.com>
On Wednesday 19 March 2008 13:23, Mike Snitzer wrote:
> > * Block layer deadlock fixes (Status: production)
>
> Do you happen to have a pointer to where these block layer deadlock
> fixes are? Or will you be committing them shortly?
Hi Mike,
OK, this is committed now, but caveat: improved, untested except for
booting. But what could possibly go wrong? :-/
http://phunq.net/ddtree?p=ddtree/.git;a=blob;f=patches/bio-throttle
The production version is sitting in the code.google.com svn repository
in ddsnap/patches/2.6.23.8. That one has a known bug that has somehow
escaped being stomped with a new commit, since it only manifests if you
stack one stacking block device on top of another one. I will post here
when we have an official, torture tested version of the patch.
The patch above is improved from the most recently posted version by
using using the ->bi_max_vecs field for throttle accounting instead of
calling out to a per-driver metric. This works nicely because the
max_vecs field cannot change during the life of the bio, and it gives
a decent upper bound on the resource consumption of the bio, better
than simply counting bios in flight. The queue->metric() method is
still in there as a stub, some more cleanup to do there (and further
shrinking of the patch). It does no harm.
This improvement shrinks the throttled version of struct bio by 4
bytes.
Regards,
Daniel
next prev parent reply other threads:[~2008-03-20 0:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 8:02 Daniel Phillips
2008-03-19 20:23 ` Mike Snitzer
2008-03-19 20:50 ` Daniel Phillips
2008-03-19 23:33 ` Daniel Phillips [this message]
2008-03-20 0:07 ` Mike Snitzer
2008-03-20 0:54 ` Mike Snitzer
2008-03-21 12:49 ` Pavel Machek
2008-03-21 18:14 ` Daniel Phillips
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=200803191633.20922.phillips@phunq.net \
--to=phillips@phunq.net \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®