From: Dan Malek <dan@mvista.com>
To: "David S. Miller" <davem@redhat.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: The IO problem on multiple PCI busses
Date: Thu, 01 Mar 2001 14:59:43 -0500 [thread overview]
Message-ID: <3A9EAA2F.7C89C88@mvista.com> (raw)
In-Reply-To: <19350124090521.18330@mailhost.mipsys.com> <15006.40524.929644.25622@pizda.ninka.net> <3A9EA3FA.1A86893B@mvista.com> <15006.42475.79484.578530@pizda.ninka.net>
"David S. Miller" wrote:
> There is only one sticking point, and that is how to convey to the
> mmap() call whether you want I/O or Memory space.
Isn't I/O space obsolete by now :-)? It actually caused me to think
of something else....I have cards with multiple memory and I/O
spaces (rare, but I have them). What if we did:
/proc/bus/pci/${BUS}/${DEVICE}/mem
/proc/bus/pci/${BUS}/${DEVICE}/io
/proc/bus/pci/${BUS}/${DEVICE}/BARn
The 'mem' or 'io' would map the first instance of these spaces
on the device, and would probably be suitable for nearly all devices.
If you really knew what you were doing (or wanted to make a big mess),
you could use the 'BARn' to specify the area.
You could even do something like map in as much virtually contiguous
space as indicated in the mmap(). For example, if the card has 2M I/O
and 8 M memory (in this order), the first 2M of the mmap()'ed space
would the the I/O and the next 8M would be the memory. I know, some
cards lie about the actual amount of space they have or need, but it
was just another idea that popped in.......
Thanks.
-- Dan
next prev parent reply other threads:[~2001-03-01 20:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-01 15:33 The IO problem on multiple PCI busses Benjamin Herrenschmidt
2001-03-01 15:41 ` Benjamin Herrenschmidt
2001-03-01 18:30 ` Alan Cox
2001-03-01 19:09 ` David S. Miller
2001-03-01 19:33 ` Dan Malek
2001-03-01 19:41 ` David S. Miller
2001-03-01 19:59 ` Dan Malek [this message]
2001-03-01 20:22 ` David S. Miller
2001-03-01 20:09 ` Benjamin Herrenschmidt
2001-03-01 20:27 ` David S. Miller
2001-03-02 11:25 ` Benjamin Herrenschmidt
2001-03-03 1:08 ` David S. Miller
2001-03-01 19:49 ` Benjamin Herrenschmidt
2001-03-01 20:21 ` David S. Miller
2001-03-01 22:26 ` Alan Cox
2001-03-02 11:20 ` Benjamin Herrenschmidt
2001-03-03 1:06 ` David S. Miller
2001-03-03 2:25 ` Benjamin Herrenschmidt
2001-03-03 11:01 ` Jeff Garzik
2001-03-03 17:28 ` Benjamin Herrenschmidt
2001-03-05 16:20 ` David Woodhouse
2001-03-06 23:01 ` Oliver Xymoron
2001-03-07 2:07 ` Tony Mantler
2001-03-05 23:21 ` Chris Wedgwood
-- strict thread matches above, loose matches on Subject: below --
2001-03-02 1:22 Grant Grundler
2001-03-02 2:19 ` David S. Miller
2001-03-02 17:46 ` Grant Grundler
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=3A9EAA2F.7C89C88@mvista.com \
--to=dan@mvista.com \
--cc=benh@kernel.crashing.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.org \
/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