[lkml]   [2002]   [Nov]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [parisc-linux] Untested port of parisc_device to generic device interface
First off, lets remember that this discussion started over two different, but 
related, problem sets. One was the DMA api and the other was the device model.

As far as the DMA API goes, consistent memory allocation has always annoyed me
because there are three separate cases

1. machine is consistent, consistent allocation always succeeds (unless we're
out of memory)

2. machine is fully inconsistent, consistent allocation always fails.

3. Machine is partially consistent. consistent allocation may fail because
we're out of consistent memory so we have to fall back to the old.

What I'd like is an improvement to the DMA API where drivers can advertise
levels of conformance (I only work with consistent memory or I work correctly
with any dma'able memory and do all the sync points), and where all the sync
point stuff optimises out for a machine architecture which is recognisably
fully consistent at compile time.

Ok, I'll get off my soapbox now. I never quite recovered from the awful
#ifdef mess that doing the above correctly for the parisc introduced into the
53c700 driver...

As far as the device model goes: said:
> No, lets start pulling stuff out of pci_dev and relying on struct
> device. The reason this hasn't happened yet is no one has been
> willing to break all of the PCI drivers, yet.

I'd like to see that. It's always annoyed me that my MCA machines have to
bounce highmem just because they don't have a pci_dev to put the bounce mask

> The SCSI people are being drug kicking and screaming into it,
> _finally_ now (hell, SCSI is still not using the updated PCI
> interface, those people _never_ update their drivers if they can avoid
> it.)

That't not entirely fair. Most of the unbroken drivers in the tree (those
with active 2.5 maintainers) are using the up to date pci/dma interface. The
mid layer is `sort of' using the device api.

Where I'd like to see the device model go for SCSI is:

- we have a device node for every struct scsi_device (even unattached ones)

- unattached devices are really minimal entities with as few resources
allocated as we can get away with, so we can have lazy attachment more easily.

- on attachment, the device node gets customised by the attachment type (and
remember, we can have more than one attachment).

- whatever the permanent `name' field for the device is going to be needs to
be writeable from user level, that way it can eventually be determined by the
user level and simply written there as a string (rather than having all the
wwn fallback cruft in the mid-layer).

- Ultimately, I'd like us to dump the host/channel/target numbering scheme in
favour of the unique device node name (we may still number them in the
mid-layer for convenience) so that we finesse the FC mapping problems---FC
devices can embed the necessary identification in the target strings.

- Oh, and of course, we move to a hotplug/coldplug model where the root device
is attached in initramfs and everything else is discovered in user space from
the boot process.

> Patches for this stuff are going to be happening for quite some time
> now, don't despair.

> And they are greatly appreciated, and welcomed from everyone :)

As far as extending the generic device model goes, I'll do it for the MCA bus.
I have looked at doing it previously, but giving the MCA bus a struct pci_dev
is a real pain because of the underlying assumptions when one of these exists
in an x86 machine.

But, while were on the subject of sorting out the device model abstraction,
does the `power' node entry really belong at the top level? It serves no
purpose for something like a legacy MCA bus.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:30    [W:0.056 / U:4.040 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site