Re: [RFC] {read,write}s{b,w,l} or iobarrier_*()
From: David S. Miller (davem@redhat.com)
Date: Thu Sep 26 2002 - 16:12:23 EST
- Next message: Thunder from the hill: "Re: [PATCH][2.5] Single linked lists for Linux, overly complicated v2"
- Previous message: Christoph Hellwig: "Re: [RFC] LSM changes for 2.5.38"
- In reply to: Jeff Garzik: "Re: [RFC] {read,write}s{b,w,l} or iobarrier_*()"
- Next in thread: Andre Hedrick: "Re: [RFC] {read,write}s{b,w,l} or iobarrier_*()"
- Reply: Andre Hedrick: "Re: [RFC] {read,write}s{b,w,l} or iobarrier_*()"
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
From: Jeff Garzik <jgarzik@pobox.com>
Date: Thu, 26 Sep 2002 12:23:41 -0400
Benjamin Herrenschmidt wrote:
> - Have all archs provide {read,write}s{b,w,l} functions.
> Those will hide all of the details of bytewapping & barriers
> from the drivers and can be used as-is for things like IDE
> MMIO iops.
I prefer this solution...
I'm starting to think about taking back all the previous
arguments I had against this idea. It's starting to sound
like the preferred way to go.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Next message: Thunder from the hill: "Re: [PATCH][2.5] Single linked lists for Linux, overly complicated v2"
- Previous message: Christoph Hellwig: "Re: [RFC] LSM changes for 2.5.38"
- In reply to: Jeff Garzik: "Re: [RFC] {read,write}s{b,w,l} or iobarrier_*()"
- Next in thread: Andre Hedrick: "Re: [RFC] {read,write}s{b,w,l} or iobarrier_*()"
- Reply: Andre Hedrick: "Re: [RFC] {read,write}s{b,w,l} or iobarrier_*()"
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
This archive was generated by hypermail 2b29
: Mon Sep 30 2002 - 22:00:28 EST