netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: benh@kernel.crashing.org
Cc: FUJITA Tomonori <tomof@acm.org>,
	hare@suse.de, open-iscsi@googlegroups.com, hch@infradead.org,
	davem@davemloft.net, mchristi@redhat.com, netdev@vger.kernel.org,
	anilgv@broadcom.com, talm@broadcom.com, lusinsky@broadcom.com,
	uri@broadcom.com, fujita.tomonori@lab.ntt.co.jp
Subject: Re: [PATCH v3 2/2][BNX2]: Add iSCSI support to BNX2 devices.
Date: Thu, 27 Sep 2007 03:49:27 -0400	[thread overview]
Message-ID: <46FB6087.10306@garzik.org> (raw)
In-Reply-To: <1190878682.30275.9.camel@pasglop>

Benjamin Herrenschmidt wrote:
> On Thu, 2007-09-27 at 03:31 -0400, Jeff Garzik wrote:
>> A key problem I was hoping would be solved with your work here was
>> the 
>> elimination of that post dma_map_sg() split.
>>
>> If I understood James and Ben correctly, one of the key problems was 
>> always in communicating libata's segment boundary needs to the IOMMU
>> layers?
> 
> Yup. If we can put some constraint in struct device that the dma mapping
> code can then look at ... we also need to ensure that what's passed in
> for DMA'ing already matches those constraints as well since no-iommu
> platforms will basically just keep the dma table as-is.

That's a good point...  no-iommu platforms would need to be updated to 
do the split for me.  I suppose we can steal that code from swiotlb or 
somewhere.

	Jeff




  reply	other threads:[~2007-09-27  7:49 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1188599815.5176.12.camel@dell>
2007-09-05 18:34 ` [PATCH v3 2/2][BNX2]: Add iSCSI support to BNX2 devices Mike Christie
2007-09-05 21:27   ` Anil Veerabhadrappa
2007-09-07 22:23     ` Mike Christie
2007-11-21 18:38       ` Anil Veerabhadrappa
2007-11-21 19:17         ` James Smart
     [not found]         ` <1195670296.8767.9.camel-opBMJL+S1+mb6IhXEaeG+wpgy58w7zIFpWgKQ6/u3Fg@public.gmane.org>
2007-11-27  4:15           ` Mike Christie
2007-11-28  0:44             ` Anil Veerabhadrappa
     [not found]               ` <1196210691.5980.20.camel-opBMJL+S1+mb6IhXEaeG+20Cxg0+/0ngpWgKQ6/u3Fg@public.gmane.org>
2007-11-28 20:06                 ` Mike Christie
2007-11-29  0:36                   ` Anil Veerabhadrappa
2007-09-08 11:59     ` Christoph Hellwig
2007-09-08 14:49       ` Michael Chan
2007-09-08 17:57         ` Anil Veerabhadrappa
2007-09-07 22:36 ` Mike Christie
2007-09-08  7:41   ` FUJITA Tomonori
2007-09-08 11:32     ` Jeff Garzik
2007-09-08 12:00       ` Christoph Hellwig
2007-09-09 15:05         ` FUJITA Tomonori
2007-09-25  8:39           ` Hannes Reinecke
2007-09-26  8:57             ` FUJITA Tomonori
2007-09-27  7:31               ` Jeff Garzik
2007-09-27  7:38                 ` Benjamin Herrenschmidt
2007-09-27  7:49                   ` Jeff Garzik [this message]
2007-09-27  8:12                     ` Benjamin Herrenschmidt
2007-09-27  8:22                       ` Jeff Garzik
2007-09-27  8:46                         ` FUJITA Tomonori
2007-09-27  8:06                 ` FUJITA Tomonori
2007-09-27  8:23                   ` Jeff Garzik

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=46FB6087.10306@garzik.org \
    --to=jeff@garzik.org \
    --cc=anilgv@broadcom.com \
    --cc=benh@kernel.crashing.org \
    --cc=davem@davemloft.net \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=hare@suse.de \
    --cc=hch@infradead.org \
    --cc=lusinsky@broadcom.com \
    --cc=mchristi@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=open-iscsi@googlegroups.com \
    --cc=talm@broadcom.com \
    --cc=tomof@acm.org \
    --cc=uri@broadcom.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 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).