From: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
To: "Leubner, Achim" <Achim_Leubner@adaptec.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Christoph Hellwig <hch@infradead.org>,
James Bottomley <James.Bottomley@SteelEye.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] fix gcc warning on 64 bit compile of gdth
Date: Tue, 4 Jan 2005 11:53:12 +0000 [thread overview]
Message-ID: <20050104115311.GD26051@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <B51CDBDEB98C094BB6E1985861F53AF302DE46@nkse2k01.adaptec.com>
On Tue, Jan 04, 2005 at 11:57:33AM +0100, Leubner, Achim wrote:
> Yes, that's the problem. I have to pass a physical address of
> scp->sense_buffer to our controller firmware that the firmware can fill
> that space with DMA after I/O. But cmdp->u.{raw,raw64}.sense_data does
> not survive until we get to unmapping stuff in gdth_sync_event() because
> there is only one cmdp structure per controller and the controller can
> handle multiple commands. So I have to save the physical address
> anywhere in the Scsi_Cmnd structure.
Umm... What about adding a new field to
struct {
Scsi_Cmnd *cmnd; /* pending request */
ushort service; /* service */
} cmd_tab[GDTH_MAXCMDS]; /* table of pend. reques
in gdth_ha_str? It's not that we couldn't change size of that animal and
AFAICS anything that might be passed to gdth_sync_event() would have to
be extracted from ha->cmd_tab[] anyway...
BTW, what uses values stored in gdth_ctr_vtab[]? It's static and gdth.[ch]
never read its elements, only set them...
next prev parent reply other threads:[~2005-01-04 11:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 10:57 [PATCH] fix gcc warning on 64 bit compile of gdth Leubner, Achim
2005-01-04 11:53 ` Al Viro [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-04 12:08 Leubner, Achim
2005-01-04 9:29 Leubner, Achim
2005-01-04 9:32 ` Arjan van de Ven
2005-01-04 10:29 ` Al Viro
2005-01-05 11:19 ` Christoph Hellwig
2005-01-04 14:55 ` James Bottomley
2005-01-05 11:19 ` Christoph Hellwig
2005-01-03 21:45 James Bottomley
2005-01-03 22:43 ` Al Viro
2005-01-03 22:49 ` James Bottomley
2005-01-03 22:54 ` Al Viro
2005-01-03 23:53 ` James Bottomley
2005-01-04 4:52 ` Al Viro
2005-01-04 8:27 ` 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=20050104115311.GD26051@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=Achim_Leubner@adaptec.com \
--cc=James.Bottomley@SteelEye.com \
--cc=arjan@infradead.org \
--cc=hch@infradead.org \
--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