On Mon, 2005-07-11 at 15:01 -0700, David S. Miller wrote: > From: Sridhar Samudrala <[EMAIL PROTECTED]> > Date: Mon, 11 Jul 2005 09:56:10 -0700 > > > An incoming skb can contain more than 1 user message(chunk) and > > we do a clone for each message and store the per-message information > > in the ulpevent structure. > > Moreover, the ulpevent structure is already 34 bytes which makes it > > impossible to share the 40-byte control block with ip specific info. > > If the sctp_chunk structure is per-user-message, and so is > the ulpevent object, it makes no sense to store the ulpevent > information seperately from sctp_chunk.
For incoming packets, the same sctp_chunk structure is used for all chunks in the packet whereas ulpevent is per-chunk. An sctp_chunk is allocated for a packet when we do a sctp_chunkify() in sctp_rcv(). We walk through the chunks in a packet and reuse the same chunk structure as we move to the next chunk(sctp_inq_pop). So we cannot keep per-message ulpevent info in sctp_chunk. Thanks Sridhar - 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
