From: Marcin Dalecki <dalecki@evision.ag>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Jens Axboe <axboe@suse.de>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.28 small REQ_SPECIAL abstraction
Date: Mon, 29 Jul 2002 15:50:27 +0200 [thread overview]
Message-ID: <3D454823.4010204@evision.ag> (raw)
In-Reply-To: 200207291344.g6TDiCR11064@localhost.localdomain
James Bottomley wrote:
> axboe@suse.de said:
>
>>Ok... I had two issues with the patch. 1) it did
>> rq->flags &= REQ_QUEUED;
>
>
> Yes, that was inherited from SCSI. Previously it just cleared flags and then
> set REQ_BARRIER|REQ_SPECIAL. Now I needed to clear flags but preserve the
> state of REQ_QUEUED, which is what that code is doing, otherwise the
> blk_rq_tagged() would always fail lower down.
>
>
>>I'll back down, it's not a matter of life and death after all. Here's
>>the minimal patch that corrects the flag thing, and also makes
>>blk_insert_request() conform to kernel style. Are we all happy?
>
>
> I'm happy (as long as it works on my SCSI card).
>
> James
BTW.> I just noticed quite a "bunch" of single line functions in the
SCIS code. Sort of like:
int scsi_warp_foo(xxx)
{
foor(whis and that);
}.
EXPORT_SYMBOL(scsi_wrap_foo);
All of them just eat space on the stack during execution.
Would you mind moving them over to scsi.h and making them static inline?
We all know that SCSI has sometimes problems with the limited stack
depth during kernel code execution time, esp on "Black Big Boxen"...
Well the above "tactics" doesn't hlep buch, but a bit is a bit is a bit
and "a man/farmer doesn't foregive someone still alive"... :-).
next prev parent reply other threads:[~2002-07-29 13:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-28 20:13 [PATCH] 2.5.28 small REQ_SPECIAL abstraction James Bottomley
2002-07-29 5:37 ` Jens Axboe
2002-07-29 5:55 ` Jens Axboe
2002-07-29 6:23 ` Linus Torvalds
2002-07-29 6:34 ` Jens Axboe
2002-07-29 6:58 ` Linus Torvalds
2002-07-29 10:43 ` Jens Axboe
2002-07-29 13:44 ` James Bottomley
2002-07-29 13:50 ` Marcin Dalecki [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-28 23:59 Andries.Brouwer
2002-07-29 0:33 ` Linus Torvalds
2002-07-29 0:52 ` Dave Jones
2002-07-30 0:50 ` Rob Landley
2002-07-24 21:13 Linux-2.5.28 Linus Torvalds
2002-07-26 6:03 ` [PATCH] 2.5.28 small REQ_SPECIAL abstraction Marcin Dalecki
2002-07-26 14:38 ` Jens Axboe
2002-07-26 15:09 ` Marcin Dalecki
2002-07-28 19:25 ` Jens Axboe
2002-07-28 23:32 ` Linus Torvalds
2002-07-29 5:39 ` Jens Axboe
2002-07-29 5:50 ` Linus Torvalds
2002-07-29 10:24 ` Marcin Dalecki
2002-07-29 10:44 ` Jens Axboe
2002-07-29 11:05 ` 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=3D454823.4010204@evision.ag \
--to=dalecki@evision.ag \
--cc=James.Bottomley@steeleye.com \
--cc=axboe@suse.de \
--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