From: Mike Christie <michaelc@cs.wisc.edu>
To: Michael Reed <mdr@sgi.com>
Cc: Douglas Gilbert <dougg@torque.net>,
linux-scsi <linux-scsi@vger.kernel.org>,
Jeremy Higdon <jeremy@sgi.com>,
James Bottomley <James.Bottomley@SteelEye.com>
Subject: Re: [PATCH] 2.6.25-rc4-git3 - inquiry cmd issued via /dev/sg? device causes infinite loop in 2.6.24
Date: Mon, 17 Mar 2008 13:08:39 -0500 [thread overview]
Message-ID: <47DEB3A7.1030600@cs.wisc.edu> (raw)
In-Reply-To: <47D7035F.5000700@sgi.com>
Michael Reed wrote:
> - ++blk_size; /* don't know why */
> -/* round request up to next highest SG_SECTOR_SZ byte boundary */
I think we can remove this code. This was asked before, and here is
Doug's reply:
http://www.mail-archive.com/linux-scsi@vger.kernel.org/msg11757.html
It was probaly due to some weirdness in that the scatterlist that sg.c
made used to be sent directly to the LLD (now it is only used to
hold/organize the pages/segments that the sg and st driver manages in
their internal reserves), or maybe it had something to do with that and
dma alignment problems or something. I really have no idea, but the
block layer SG IO code has not been rounding up in its indirect path and
it has been fine.
next prev parent reply other threads:[~2008-03-17 18:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 22:10 [PATCH] 2.6.25-rc4-git3 - inquiry cmd issued via /dev/sg? device causes infinite loop in 2.6.24 Michael Reed
2008-03-12 10:46 ` Boaz Harrosh
2008-03-12 16:03 ` Michael Reed
2008-03-12 16:09 ` Boaz Harrosh
2008-03-14 13:11 ` Michael Reed
2008-03-18 16:12 ` Michael Reed
2008-03-18 16:20 ` Boaz Harrosh
2008-03-18 16:52 ` Michael Reed
2008-03-18 17:19 ` Boaz Harrosh
2008-03-19 15:57 ` Michael Reed
2008-03-19 16:18 ` Boaz Harrosh
2008-03-19 21:34 ` Michael Reed
2008-03-18 17:13 ` Michael Reed
2008-03-18 18:23 ` Boaz Harrosh
2008-03-18 19:51 ` Michael Reed
2008-03-19 9:49 ` Boaz Harrosh
2008-03-17 18:08 ` Mike Christie [this message]
2008-03-18 0:48 ` FUJITA Tomonori
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=47DEB3A7.1030600@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=James.Bottomley@SteelEye.com \
--cc=dougg@torque.net \
--cc=jeremy@sgi.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mdr@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.