The "result" of one async operation is basically a cookie and a result
code. Eight or sixteen bytes at most.
s/basically/minimally/
Well, yeah. The patches I sent had:
struct asys_completion {
long return_code;
unsigned long cookie;
};
That's as stupid as it gets.
IMO, before going wacko designing
complex shared userspace-kernel result buffers, I think it'd be better
measuring the worth-value of the thing ;)
Obviously, yes.
The potential win is to be able to have one place to wait for
collection from multiple sources. Some of them might want more data
per event. They can always indirect out via a cookie pointer, sure,
but at insanely high message rates (10gige small messages) one might
not want that.
See also: the kevent thread.
- z
-
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/
