[EMAIL PROTECTED] wrote:
>> For instance, would or would not udp_rput be required to pass up the
>> meta data so that a "module" above could inspect it?
>> Would a kernel socket API have to pass it up?
>
>
> I hadn't considered either of these two scenarios.
> In the requirements I've seen so far, there is no
> requirement for the meta data to follow the data itself.
>
>> Should TCP use it for response traffic or not?
>> What about forwarding.
>
>
> For packets being forwarded through the kernel, meta data
> that is attached to a packet should be preserved until either
> the packet is freed/discarded (this includes after it is sent
> out of the NIC) or the owner disposes of it (it/when they see
> it again).
Are you saying that the requirements you've seen limit themselves to
carrying the data around in layer 3 functions? (No need for transports
or applications to see it.)
Erik
_______________________________________________
networking-discuss mailing list
[email protected]
