From: Boaz Harrosh <bharrosh@panasas.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Matthew Dharm <mdharm-usb@one-eyed-alien.net>,
USB list <linux-usb@vger.kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
linux-scsi <linux-scsi@vger.kernel.org>,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH 0/4] Use of new scsi_allocate_command
Date: Thu, 01 May 2008 18:59:03 +0300 [thread overview]
Message-ID: <4819E8C7.3040808@panasas.com> (raw)
In-Reply-To: <1209656838.3067.16.camel@localhost.localdomain>
On Thu, May 01 2008 at 18:47 +0300, James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> On Thu, 2008-05-01 at 18:36 +0300, Boaz Harrosh wrote:
>> On Thu, May 01 2008 at 18:22 +0300, James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
>>> On Thu, 2008-05-01 at 17:56 +0300, Boaz Harrosh wrote:
>>>> The call to pci_map_page() on an ISA case will it not bounce the
>>>> buffer?
>>> Only if the system isn't a PCI_DMA_BUS_IS_PHYS one.
>>>
>>> That means basically either has an iommu/gart or has some silly swiotlb
>>> to emulate one.
>>>
>>> That means for standard x86 isa systems the answer is no: the buffer has
>>> to be allocated within the isa region because pci_map is simply a
>>> virt_to_phys.
>>>
>>> James
>>>
>> OK Thanks, so the second patch then. That will solve it.
>
> Um, your second patch is only changing isd200; it's hard to see how that
> can fix a gdth problem ...
>
> James
>
>
Sorry I meant the second version of the patch that uses scsi_get_command()
http://marc.info/?l=linux-scsi&m=120965483126936&w=2
Boaz
next prev parent reply other threads:[~2008-05-01 15:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4819C9DB.60104@panasas.com>
2008-05-01 13:56 ` [PATCH 1/4] scsi_free_command API change - Don't support GFP_DMA Boaz Harrosh
2008-05-01 13:58 ` [PATCH 2/4] isd200: Use new scsi_allocate_command() Boaz Harrosh
2008-05-01 14:02 ` [PATCH 3/3] gdth: consolidate __gdth_execute && gdth_execute Boaz Harrosh
2008-05-01 14:06 ` [PATCH 4/4] gdth: Use scsi_allocate_command for private command allocation Boaz Harrosh
2008-05-01 14:24 ` [PATCH 0/4] Use of new scsi_allocate_command James Bottomley
[not found] ` <1209651854.3067.8.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-05-01 14:56 ` Boaz Harrosh
2008-05-01 15:13 ` Boaz Harrosh
2008-05-01 15:22 ` James Bottomley
2008-05-01 15:36 ` Boaz Harrosh
[not found] ` <4819E371.2040403-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
2008-05-01 15:47 ` James Bottomley
2008-05-01 15:59 ` Boaz Harrosh [this message]
2008-05-01 16:02 ` James Bottomley
[not found] ` <1209657731.3067.19.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-05-01 16:25 ` Boaz Harrosh
2008-05-01 16:38 ` James Bottomley
2008-05-01 17:06 ` Boaz Harrosh
2008-05-01 17:33 ` James Bottomley
[not found] ` <1209663229.14864.18.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-05-01 18:14 ` Boaz Harrosh
2008-05-01 20:32 ` James Bottomley
[not found] ` <1209673979.14864.23.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-05-01 21:41 ` Andi Kleen
2008-05-01 13:47 Boaz Harrosh
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=4819E8C7.3040808@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=andi@firstfloor.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mdharm-usb@one-eyed-alien.net \
--cc=stern@rowland.harvard.edu \
/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).