Thanks for your comments!
I'd like to better understand your dislike of the current implementation
of the data transfer from user space to kernel space.
Is it the fact that we use configfs?
I think, we had already a discussion about this (and we changed from
procfs to configfs).
Or don't you like that we need a user space daemon which is responsible
for feeding the data to the kernel module?
I think we do not have another option, since the trace file may be of
arbitrary length.
Or anything else?
Patrick McHardy wrote:
Stephen Hemminger wrote:
Still interested in this. I got part way through integrating it but had
concerns about the API from the application to netem for getting the
data.
It seemed like there ought to be a better way to do it that could
handle large
data sets better, but never really got a good solution worked out
(that is why
I never said anything).
Would spreading them over multiple netlink messages work? A different,
slightly ugly possibility would be to simply use copy_from_user, netlink
is synchronous now (still better than using configfs IMO).
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
