From: Jonathan Lahr <lahr@us.ibm.com>
To: Jens Axboe <axboe@suse.de>
Cc: lahr@eng2.beaverton.ibm.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: Re: [Lse-tech] SCSI io_request_lock patch
Date: Thu, 15 Nov 2001 10:15:43 -0800 [thread overview]
Message-ID: <20011115101543.R26302@us.ibm.com> (raw)
In-Reply-To: <20011112130902.B26302@us.ibm.com> <20011113092311.L786@suse.de> <20011113104210.L26302@us.ibm.com> <20011114091129.H17933@suse.de> <20011114105433.O26302@us.ibm.com> <20011115112300.S27010@suse.de>
In-Reply-To: <20011115112300.S27010@suse.de>; from axboe@suse.de on Thu, Nov 15, 2001 at 11:23:00AM +0100
Jens Axboe [axboe@suse.de] wrote:
> On Wed, Nov 14 2001, Jonathan Lahr wrote:
> > > It's absolutely worthless. Look, it ties in with the points I made
> > > below. You are exporting the merge functions for instance, and setting
> > > them in the queue. This will cause scsi_merge not to use it's own
> > > functions, broken.
> >
> > As in the baseline, initialize_merge_fn overwrites these pointers:
> > q->back_merge_fn = scsi_back_merge_fn_;
> > q->front_merge_fn = scsi_front_merge_fn_;
> > q->merge_requests_fn = scsi_merge_requests_fn_;
>
> I had forgotten I had #if 0 out the check for already set back_merge etc
> in scsi_merge -- however that's still beside the point. _Why_ are you
> exporting the ll_rw_blk functions and setting them just to have them
> overridden? Makes no sense.
...
> Don't export the merge functions ever, define your own if you really
> need them. You don't, though.
That resulted merely from basing scsi_init_queue on blk_init_queue.
I'll simplify the code by removing these unnecessary assignments.
--
Jonathan Lahr
IBM Linux Technology Center
Beaverton, Oregon
lahr@us.ibm.com
503-578-3385
prev parent reply other threads:[~2001-11-15 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 21:09 SCSI io_request_lock patch Jonathan Lahr
2001-11-13 8:23 ` [Lse-tech] " Jens Axboe
2001-11-13 18:42 ` Jonathan Lahr
2001-11-14 8:11 ` Jens Axboe
2001-11-14 18:54 ` Jonathan Lahr
2001-11-15 10:23 ` Jens Axboe
2001-11-15 18:15 ` Jonathan Lahr [this message]
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=20011115101543.R26302@us.ibm.com \
--to=lahr@us.ibm.com \
--cc=axboe@suse.de \
--cc=lahr@eng2.beaverton.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
/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