Messages in this thread | | | Date | Thu, 20 Apr 2006 16:26:54 -0700 (PDT) | From | David Lang <> | Subject | Re: Linux 2.6.17-rc2 |
| |
On Thu, 20 Apr 2006, Linus Torvalds wrote:
> (Some users may even be able to take _advantage_ of the fact that the > buffer is "in flight" _and_ mapped into user space after it has been > submitted. You could imagine code that actually goes on modifying the > buffer even while it's being queued for sending. Under some strange > circumstances that may actually be useful, although with things like > checksums that get invalidated by you changing the data while it's queued > up, it may not be acceptable for everything, of course).
I could see this in some sort of logging/monitoring situation where you want the latest data you can possibly get at each write. with the appropriate care in write ordering you could have one thread update the buffer continuously and the buffer gets written out periodicly, what gets written is the latest possible info.
definantly not a common case, but I could see it's use in some cases.
David Lang
-- There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies. -- C.A.R. Hoare
- 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/
| |