From: David Miller <davem@davemloft.net>
To: James.Bottomley@SteelEye.com
Cc: hch@infradead.org, stefanr@s5r6.in-berlin.de,
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 13:37:30 -0700 (PDT) [thread overview]
Message-ID: <20070515.133730.120446537.davem@davemloft.net> (raw)
In-Reply-To: <1179248245.3685.23.camel@mulgrave.il.steeleye.com>
From: James Bottomley <James.Bottomley@SteelEye.com>
Date: Tue, 15 May 2007 12:57:25 -0400
> It might make sense to put it in lib ... however, I don't think many
> architectures have the problems we have ... specifically certain boxes
> can have >1 IOMMU, then you really have to know *which* iommu you're
> programming.
Sparc64 boxes will have this at some point, but what I'm
going to do is simply fill in the dev_archdata properly at
device scan time.
Instead of doing a bus walk up the parent every IOMMU request, why not
cache those results in the dev_archdata? That seems to make the most
sense.
If there is some probing complexity, catch not-setup dev_archdata at
the IOMMU request, and slow path into a resolver of some sort.
next prev parent reply other threads:[~2007-05-15 20:37 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
2007-05-15 16:57 ` James Bottomley
2007-05-15 20:37 ` David Miller [this message]
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=20070515.133730.120446537.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=James.Bottomley@SteelEye.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hch@infradead.org \
--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