Re: [PATCH 0/6] PCI-X/PCI-Express read control interfaces

> I am thinking in the next revision of these of masking the distinction
> between pci-x and pci express and just have:
> 
> pci_get_read_count
> pci_get_max_read_count
> pci_set_read_count

We absolutely need an arch hook though to limit the size. We need to
make sure we don't go over the capabilities of parent bridges,
especially the host bridge. P2P bridges and most PCIe host bridges can
be handled by generic code but pretty much no PCI-X host bridge, they'll
need an arch hook.

Ben.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH 0/6] PCI-X/PCI-Express read control interfaces
    • From: Stephen Hemminger <[email protected]>
  • Re: [PATCH 0/6] PCI-X/PCI-Express read control interfaces
    • From: Benjamin Herrenschmidt <[email protected]>
  • Re: [PATCH 0/6] PCI-X/PCI-Express read control interfaces
    • From: Stephen Hemminger <[email protected]>

• Prev by Date: Processes with hidden PID files in /proc
• Next by Date: Re: Bug: early_pfn_in_nid() called when not early
• Previous by thread: Re: [PATCH 0/6] PCI-X/PCI-Express read control interfaces
• Next by thread: Loud POP from sound system during module init w/ 2.6.19
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]