Hi Evgeniy,

If you _do_ want to make it that way, you can remove destructor at all
and implement own packet-socket-only allocation policy and thus have own
private destructor without extending skb.

Currently, we are executing sock_alloc_send_skb() to allocate a new
skb from socket.
Then, we replace destructor sock_wfree() with our destructor
packet_skb_destruct() which executes sock_wfree() once status of
packet frame (associated to skb data) has been given back to user
(status changed).

Is this way ok ?
Or shall we implement our own sock_alloc_send_skb()?

Thanks in advance,
Johann


-- 
Johann Baudy
johaahn@gmail.com