From: "Peter T. Breuer" <ptb@it.uc3m.es>
To: Jens Axboe <axboe@suse.de>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: floppy driver 2.6.3 question
Date: Thu, 18 Mar 2004 19:11:01 +0100 (MET) [thread overview]
Message-ID: <200403181811.i2IIB1f18197@oboe.it.uc3m.es> (raw)
In-Reply-To: <20040318161647.GT22234@suse.de> from Jens Axboe at "Mar 18, 2004 05:16:48 pm"
"Also sprach Jens Axboe:"
> > I mean that I thought that if ->flags & REQ_SPECIAL were set, then
> > we were obliged to flush the driver request queue before treating
> > this request, and I also thought that the driver was liable to receive
> > such things from somewhere else.
>
> I dunno where you get those crazy ideas, REQ_SPECIAL has absolutely
> nothing to do with that.
Sorry about that. Perhaps I saw it in 2.5.
> You may use REQ_SPECIAL bit as you see fit, and ->special as well. You
> don't have to use them together, must do though. However, as I said
> earlier, if you push these requests on to someone else request queue,
> you must not fiddle with REQ_SPECIAL and/or ->special. In that case you
> cannot touch/use more than what the block layer already does.
Well hooray. All seems to be working fine now that I shifted the burden
to ->special and stopped playing with ->flags (touch wood). Even
revalidation is working AOK as far as I can tell. I'll reenable that
read of the first block a-la-floppy to see if it causes some extra magic.
Many thanks!
> > Are you going to say, set REQ_SPECIAL on everything and add all the
> > real request info and a bit more to ->special? I suspect you are!
>
> That's where to put it, indeed. But if you pass it on...
Peter
next prev parent reply other threads:[~2004-03-18 18:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 20:02 Peter T. Breuer
2004-03-18 7:14 ` Jens Axboe
2004-03-18 8:23 ` Peter T. Breuer
2004-03-18 9:10 ` Jens Axboe
2004-03-18 10:05 ` Peter T. Breuer
2004-03-18 11:35 ` Jens Axboe
2004-03-18 12:23 ` Peter T. Breuer
2004-03-18 12:28 ` Jens Axboe
2004-03-18 13:25 ` Peter T. Breuer
2004-03-18 13:31 ` Jens Axboe
2004-03-18 16:06 ` Peter T. Breuer
2004-03-18 16:16 ` Jens Axboe
2004-03-18 18:11 ` Peter T. Breuer [this message]
2004-03-18 19:05 ` 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=200403181811.i2IIB1f18197@oboe.it.uc3m.es \
--to=ptb@it.uc3m.es \
--cc=axboe@suse.de \
--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 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®