From: Christoph Hellwig <hch@lst.de>
To: osst@riede.org
Cc: linux-scsi@vger.kernel.org
Subject: osst changes required to move forward to block request
Date: Mon, 6 Feb 2006 14:19:44 +0100 [thread overview]
Message-ID: <20060206131944.GA1769@lst.de> (raw)
Hi Willem,
do you still maintain the osst driver? We're moving forward to
completly get rid of the scsi_request structure in the scsi midlayer,
and osst is the only upper level driver still using it. I've tried to
convert it similar to st, but gave up. The biggest problem for me is
the scsi_request reuse over the driver where a pointer to a pointer to
a scsi_request is passed along all the callchain, and I have a really
hard time to find out whether the functions actually looks it, or only
reuse it. The latter isn't nessecary these days that the slab allocator
behind struct scsi_request does a very good job, and definitly not
needed after converting away from it.
If you're still interested in the driver it would be very nice if you
could untangle it so that the scsi_request is only passed along in
places where subroutines need to look at it - after that converting
the driver should be more along the lines of st so a lot easier. I'd
be more than happy to lend a helping hand or to in the conversion once
I actually understand what I'm doing :) It would be a pity to either
stop the scsi subsystem from moving forward because of osst or breaking
the driver.
p.s. there's quite a few other changes in st that osst hasn't caught up
on, maybe it's time for a big resync?
next reply other threads:[~2006-02-06 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 13:19 Christoph Hellwig [this message]
2006-02-07 1:02 ` osst changes required to move forward to block request Willem Riede
2006-02-07 9:12 ` Christoph Hellwig
2006-02-11 19:46 ` Willem Riede
2006-02-14 19:24 ` Christoph Hellwig
2006-02-19 20:27 ` Willem Riede
2006-03-07 11:59 ` Christoph Hellwig
2006-03-07 21:53 ` James Bottomley
2006-03-07 22:16 ` Willem Riede
2006-03-07 22:43 ` Christoph Hellwig
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=20060206131944.GA1769@lst.de \
--to=hch@lst.de \
--cc=linux-scsi@vger.kernel.org \
--cc=osst@riede.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 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.