From: Jens Axboe <axboe@suse.de>
To: martin@dalecki.de
Cc: Petr Vandrovec <VANDROVE@vc.cvut.cz>,
linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] 2.5.30 IDE 113
Date: Tue, 6 Aug 2002 13:12:24 +0200 [thread overview]
Message-ID: <20020806111224.GG1323@suse.de> (raw)
In-Reply-To: <3D4FAD3A.1090309@evision.ag>
On Tue, Aug 06 2002, Marcin Dalecki wrote:
> Uz.ytkownik Jens Axboe napisa?:
>
> >Agrh god no. So you'll spin waiting for the ioctl to complete?
> >
> >>From ide_raw_taskfile(), the right way to do it is:
> >
> > struct request *rq = blk_get_request(...);
> >
> >This gets _everything_ right.
> >
> >BTW, _glad to see you got rid of the horrible insert-and-execute stuff
> >in ide_raw_taskfile(). That was a layering violation.
> >
> >
> >>OK?
> >
> >
> >Not likely :-)
>
> Argh. Yes. Thank's for the back-head slap.
> I was looking too much at the SCSI code again and got it wrong.
> But some time ago I was already thinking about blk_get_request().
> How could I maintain that the blk_get_request() really returns?
> blk_get_request() does only drain up to maximum queue depth as
> far as I can read the code and then bad things wil happen :-).
> Or should I just not worry?
You can make it do what you want. From ioctl etc context (or basically
anyone calling ide_raw_taskfile() since that will block too), you can
use a blocking call to blk_get_request(). So
rq = blk_get_request(q, WRITE, __GFP_WAIT);
will _never_ return NULL. You are basically throttling on the freelist
of the queue, just like any other submitter of I/O. And that, is a Good
Thing :-)
--
Jens Axboe
next prev parent reply other threads:[~2002-08-06 11:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 10:35 [PATCH] 2.5.30 IDE 113 Petr Vandrovec
2002-08-06 10:44 ` Jens Axboe
2002-08-06 10:47 ` Marcin Dalecki
2002-08-06 11:03 ` Jens Axboe
2002-08-06 11:04 ` Marcin Dalecki
2002-08-06 11:12 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-06 10:16 Petr Vandrovec
2002-08-06 10:20 ` Marcin Dalecki
2002-08-06 10:42 ` Jens Axboe
2002-08-06 10:43 ` Marcin Dalecki
2002-08-06 10:54 ` Jens Axboe
2002-08-06 10:52 ` Marcin Dalecki
2002-08-06 11:05 ` Jens Axboe
2002-08-06 11:09 ` Marcin Dalecki
2002-08-06 11:17 ` Jens Axboe
2002-08-06 11:57 ` Marcin Dalecki
2002-08-06 9:02 Marcin Dalecki
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=20020806111224.GG1323@suse.de \
--to=axboe@suse.de \
--cc=VANDROVE@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@dalecki.de \
--cc=torvalds@transmeta.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