From: Jon Escombe <lists@dresco.co.uk>
To: Jens Axboe <axboe@suse.de>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
hdaps-devel@lists.sourceforge.net
Subject: Re: [RFC] Hard disk protection revisited
Date: Fri, 07 Oct 2005 13:04:35 +0100 [thread overview]
Message-ID: <43466453.9070604@dresco.co.uk> (raw)
In-Reply-To: <20051007100219.GU2889@suse.de>
Jens Axboe wrote:
>I have to nack this one for now, I still want the generic command types
>patch to go in first. We have far too many queue hooks already, adding
>two more for a relatively obscure use such as this one is not a good
>idea.
>
>My suggestion is to maintain this patch out of tree for now, it will be
>a few kernel release iterations before the command type patch is in.
>
>
That's a fair comment (and not entirely unexpected), I don't have a
problem with looking after this out of tree for now...
One issue with the generic command approach occured to me while making
this patch - although it's more likely an issue with my understanding ;)
I'm assuming that it would work like this -- the block layer still has
the sysfs attribute, and queues the new command for the lower driver to
pick up. The driver receives the command and does it's custom
park/freeze work, then calls a common block layer function to setup the
timer (all good so far). Where it gets hazy (for me) is how the block
layer starts the queue up again - as this ended up needing to be driver
specific & I can't see how the block layer would get another command
down if the queue is stopped?
Regards,
Jon.
______________________________________________________________
Email via Mailtraq4Free from Enstar (www.mailtraqdirect.co.uk)
next prev parent reply other threads:[~2005-10-07 12:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 23:24 [RFC] Hard disk protection revisited Jon Escombe
2005-10-06 23:24 ` Jon Escombe
2005-10-07 10:02 ` Jens Axboe
2005-10-07 12:04 ` Jon Escombe [this message]
2005-10-07 12:11 ` Jens Axboe
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=43466453.9070604@dresco.co.uk \
--to=lists@dresco.co.uk \
--cc=axboe@suse.de \
--cc=hdaps-devel@lists.sourceforge.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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.