From: Jens Axboe <axboe@suse.de>
To: "Govindan, Thiru" <GovinT@LOUISVILLE.STORTEK.COM>
Cc: "'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>
Subject: Re: FW: Re. Allocation of scatter gather table in __init_io
Date: Mon, 9 Aug 2004 11:14:37 +0200 [thread overview]
Message-ID: <20040809091436.GU10418@suse.de> (raw)
In-Reply-To: <E5A17223DA27AB4DABB18A5955F4235545CFD2@EXCHVS1.louisville.stortek.com>
(don't top post, reply properly commented below the questions asked like
everybody else is doing)
On Mon, Aug 09 2004, Govindan, Thiru wrote:
> Jens,
> Ok, but __init_io() does seem to expect that the number of segments
> matches the count after merging is done. As shown in the code below, if its
> OK to allocate space for the max. number of items then this check is not
> needed.
> /*
> * Verify that the count is correct.
> */
> if (count != SCpnt->use_sg) {
> printk("Incorrect number of segments after building
> list\n");
> #ifdef CONFIG_SCSI_DEBUG_QUEUES
> dump_stats(req, use_clustering, dma_host, count);
> #endif
> }
Ah, you are talking about 2.4 (in the future, remember to note which
kernel base you are talking about). Yes those counts must match, if not
something is broken in the merging code.
> How does the HBA driver know the correct number in this case? Should
> it use request_bufflen in the SCSI Command in addition to use_sg, to
> identify the number of segments actually there in the list? I'm using
> a Qlogic HBA and its just going by the value in use_sg to identify
> segments in the scatter-gather list.
I don't completely follow your question, sorry. Can you outline in
detail what happens, what values you are seeing, etc.
--
Jens Axboe
next prev parent reply other threads:[~2004-08-09 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 9:09 FW: Re. Allocation of scatter gather table in __init_io Govindan, Thiru
2004-08-09 9:14 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-09 4:50 Govindan, Thiru
2004-08-09 8:36 ` 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=20040809091436.GU10418@suse.de \
--to=axboe@suse.de \
--cc=GovinT@LOUISVILLE.STORTEK.COM \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).