[Top] [All Lists]

Re: [PATCH] merge sctp_opt with sctp_sock

To: "David S. Miller" <davem@xxxxxxxxxxxxx>
Subject: Re: [PATCH] merge sctp_opt with sctp_sock
From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxxxxxxxx>
Date: Mon, 17 Jan 2005 23:12:13 -0200
Cc: sri@xxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <>
Organization: Conectiva S.A.
References: <> <>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0 (X11/20041220)
David S. Miller escreveu:
On Sat, 15 Jan 2005 02:52:13 -0200
Arnaldo Carvalho de Melo <acme@xxxxxxxxxxxxxxxx> wrote:

        Please take a look and if its acceptable pull from:


        The tricky bit here is that SCTP, to keep the existing logic,
needs a way to copy only its private area from one sock to another, so
I introduced a generic inet_sk_copy_descendant, that knows about the
inet (v4/v6) layout (wrt inet_sock and inet6_pinfo), using this and
sk->sk_prot->slab_obj_size we can copy the inet_sock descendant
private area generically.

This looks fine, although I wish the descendant copying thing
could be done more cleanly somehow.

/me too, but this is the best scheme I've found for now, perhaps in the future, after some more refactoring work is done/merged we can find some better way of doing this (tcp_create_openreq_child also does something like this, but does it in all the sock, perhaps SCTP can do something similar).

In fact my ambition is after mucho refactoring have some common
infrastructure even for child creation.

OK, back to chainsawing net/{ax25,netrom,rose} into a state where we
can actually use a slab cache for each of them, which is needed to
get the connection_sock abstraction into place, most of the work is
done, now I'm reading some HAM radio howtos and preparing a testbed
using bpqether, etc. Oh, there is another legacy family to send to
you first: IPv6 ;)



- Arnaldo

<Prev in Thread] Current Thread [Next in Thread>