Hi,
Yes, but ...
On Wed, Jul 13, 2005 at 10:18:57AM +1000, Benjamin Herrenschmidt was heard to
remark:
>
> > Are you assuming that a device driver will use an iochk_read() for
> > every DMA operation? for every MMIO to the card?
> >
> > For high performance devices, it seems to me that this
Linas Vepstas wrote:
Thus, one wouldn't want to perform an iochk_read() in this way unless
one was already pretty sure that an error had already occured ...
If another kind of I/O error detecting system finds a error before
performing iochk_read(), it can prevents coming iochk_read() from
spen
> Are you assuming that a device driver will use an iochk_read() for
> every DMA operation? for every MMIO to the card?
>
> For high performance devices, it seems to me that this will cause
> a rather large performance burden, especially if its envisioned that
> all architectures will do someth
Hi,
Sorry for the late response ...
I'm reading the patch, and I'm wondering what about performance and
overhead. Here's the code that concerns me:
On Wed, Jul 06, 2005 at 02:04:14PM +0900, Hidetoshi Seto was heard to remark:
> [This is 3 of 10 patches, "iochk-03-register.patch"]
>
> - Impl
[This is 3 of 10 patches, "iochk-03-register.patch"]
- Implement ia64 version of basic codes:
iochk_clear, iochk_read, iochk_init, and iocookie
The direction is:
- Have a "now in check" global list, "iochk_devices",
for future use.
- Take a lock, "iochk_lock", to protect th
5 matches
Mail list logo
