From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Sridhar Samudrala <sri@us.ibm.com>
Cc: "David S.Miller" <davem@redhat.com>,
YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>,
netdev@oss.sgi.com
Subject: Re: [PATCH][NET] generalise per socket slab cache use
Date: Mon, 13 Sep 2004 18:51:08 -0300 [thread overview]
Message-ID: <200409131851.10705.acme@conectiva.com.br> (raw)
In-Reply-To: <Pine.LNX.4.58.0409131410540.19499@localhost.localdomain>
Em Seg 13 Set 2004 18:17, Sridhar Samudrala escreveu:
> Arnaldo,
>
> looks good, but i have a few comments. It is great that SCTP now has its
> own slabcaches.
>
> > +struct ipv6_sk_offset raw_sock_offset = {
> > + .offset = offsetof(struct udp6_sock, inet6),
> > +};
>
> I think there is a typo here. udp6_sock should be raw6_sock
Good spotting! I'll fix this one
> > - printk(KERN_CRIT "%s: Can't create protocol sock SLAB "
> > - "caches!\n", __FUNCTION__);
>
> You have removed the above critical messages. Is this by intent or a
> mistake.
Humm, I'll put it on the sk_alloc_slab callers
>
> I am not clear on why we need this new structure ipv6_sk_offset.
>
> > +struct ipv6_sk_offset {
> > + int offset;
> > +};
> > +
>
> Instead of adding the new field void *af_specific to struct proto, is it
> not sufficient to add
> int pinet6_offset;
>
> and assign it as follows for each v6 sock type
> .pinet6_offset = offsetof(struct struct tcp6_sock, inet6)
>
> In inet6_sk_generic(), you can directly use sk->sk_prot->pinet6_offset.
I thought about it, but idea was to not introduce any family specific stuff in
struct proto, I don't plan to have LLC over IPv6, for instance :)
> Thanks
> Sridhar
next prev parent reply other threads:[~2004-09-13 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-11 3:23 [PATCH][NET] generalise per socket slab cache use Arnaldo Carvalho de Melo
2004-09-13 21:17 ` Sridhar Samudrala
2004-09-13 21:51 ` Arnaldo Carvalho de Melo [this message]
2004-09-13 22:55 ` David S. Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200409131851.10705.acme@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=sri@us.ibm.com \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).