Re: question regarding cacheline size

> 
> So I think we should redo the PCI subsystem to set cacheline size during
> the buswalk rather than waiting for drivers to ask for it to be set.

... while allowing for quirks for devices that go puke when this
register gets written ;)

(afaik there are a few)



-
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/

---

• Follow-Ups:
  • Re: question regarding cacheline size
    • From: Matthew Wilcox <[email protected]>

• References:
  • question regarding cacheline size
    • From: Tejun Heo <[email protected]>
  • Re: question regarding cacheline size
    • From: Matthew Wilcox <[email protected]>
  • Re: question regarding cacheline size
    • From: Tejun Heo <[email protected]>
  • Re: question regarding cacheline size
    • From: Russell King <[email protected]>
  • Re: question regarding cacheline size
    • From: Matthew Wilcox <[email protected]>

• Prev by Date: Re: [PATCH] fail kernel compilation in case of unresolved symbols (v2)
• Next by Date: Re: question regarding cacheline size
• Previous by thread: Re: question regarding cacheline size
• Next by thread: Re: question regarding cacheline size
• 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]