From: Christoph Hellwig <hch@infradead.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
linux-scsi@vger.kernel.org, jens.axboe@oracle.com
Subject: Re: [PATCH 0/19] clean ups on the drivers
Date: Tue, 15 May 2007 12:57:48 +0100 [thread overview]
Message-ID: <20070515115748.GA12461@infradead.org> (raw)
In-Reply-To: <1179230056.3685.2.camel@mulgrave.il.steeleye.com>
On Tue, May 15, 2007 at 06:54:16AM -0500, James Bottomley wrote:
> Er ... I really hope not ... that's exactly how the parisc iommu
> platform code works ... and why I designed the generic dma mapping this
> way. The key thing parisc needed was the ability to walk up different
> busses until it found the iommu (for example the pci bus -> dino -> GSC
> -> IOMMU) which it does by traversing the dev->parent; However, I didn't
> mandate working this way for other architectures.
Well, the NACK was not for the implementation details but rather the
exported and documented interface. IIRC the rationale was that Dave wants
to keep the sparc implementation super-optimized and avoid indirection.
If it was up to me I'd have something like the parisc implementation in
generic code.
next prev parent reply other threads:[~2007-05-15 11:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 10:05 [PATCH 0/19] clean ups on the drivers FUJITA Tomonori
2007-05-12 15:30 ` Christoph Hellwig
2007-05-13 3:30 ` FUJITA Tomonori
2007-05-14 14:40 ` FUJITA Tomonori
2007-05-14 15:39 ` Stefan Richter
2007-05-14 22:36 ` FUJITA Tomonori
2007-05-15 9:01 ` Christoph Hellwig
2007-05-15 11:54 ` James Bottomley
2007-05-15 11:57 ` Christoph Hellwig [this message]
2007-05-15 16:57 ` James Bottomley
2007-05-15 20:37 ` David Miller
2007-05-15 20:49 ` James Bottomley
2007-05-22 23:32 ` 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=20070515115748.GA12461@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@SteelEye.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jens.axboe@oracle.com \
--cc=linux-scsi@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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