From: Grant Grundler <grundler@dsl2.external.hp.com>
To: Ryan Bradetich <rbradetich@uswest.net>
Cc: Juergen Braukmann <juergen.braukmann@ruhr-west.de>,
parisc list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Kernel panic, ccio-dma.c, C110
Date: Fri, 19 Jul 2002 01:17:58 -0600 [thread overview]
Message-ID: <20020719071758.A865B4834@dsl2.external.hp.com> (raw)
In-Reply-To: Message from Ryan Bradetich <rbradetich@uswest.net> of "17 Jul 2002 17:53:00 MDT." <1026949980.10285.4.camel@beavis>
Ryan Bradetich wrote:
> Is there a way to make this more intelligent now that we have an I/O tree?
Probably. I'm looking at info given by "lspci -n".
o generalize characteristics of each PCI device class/subclass and
assign them a score.
o sum scores by recursively walking all the PCI busses below an IOMMU.
o translate the total score into how much memory could be mapped at
a time (ie size of IO pdir)
o make sure IO Pdir size can't map more than 50% or 75% of Host
physical memory.
> Maybe driverfs in 2.5.X will help us figure out how to make it
> smarter ... it kinda sucks to recompile the kernel because you do not
> have enough memory for our default setting of 4.
driver fs would probably help since we could then do it the
same way for all bus types.
But in 2.5, I'd rather see all the drivers indicate "Max DMA Mappings"
in some static data since that's what is really driving
the IO Pdir size.
> Seems like we could develop a huristic based on devices below the
> iommus.
yup. Will need tweaks too though...just satisfies more people.
grant
next prev parent reply other threads:[~2002-07-19 7:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 15:50 [parisc-linux] Kernel panic, ccio-dma.c, C110 Juergen Braukmann
2002-07-17 17:57 ` joel.soete
2002-07-17 18:14 ` Grant Grundler
2002-07-17 23:53 ` Ryan Bradetich
2002-07-19 7:17 ` Grant Grundler [this message]
2002-07-18 5:37 ` joel.soete
2002-07-18 15:19 ` Juergen Braukmann
2002-07-18 16:28 ` Juergen Braukmann
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=20020719071758.A865B4834@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=juergen.braukmann@ruhr-west.de \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=rbradetich@uswest.net \
/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