From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: "David S. Miller" <davem@davemloft.net>
Cc: Networking Team <netdev@oss.sgi.com>
Subject: [PATCH 0/12] remove sk_protinfo series
Date: Fri, 21 Jan 2005 01:18:47 -0200 [thread overview]
Message-ID: <41F07497.4020109@conectiva.com.br> (raw)
Hi David,
This series addresses Christoph and Jean concerns about the overhead
caused by private slab caches in every family, by making sk_alloc use kmalloc
if no slab cache is used, and as a transitional mechanism the zero_it
semantic is maintained, that is, if slab is NULL and zero_it is 1, use the
generic "slab" (sk_cachep) cache.
Now only the ham radio protocols (AX25, NETROM and ROSE) and
net/wanrouter uses sk_protinfo to store an private area directly, and
bluetooth uses it as a second level for proto info while using a
private slab cache for the first level of proto info.
This series has atm and pppox in addition to the set of families
covered in the first series.
Available at:
bk://kernel.bkbits.net/acme/connection_sock-2.6
Best Regards,
- Arnaldo
next reply other threads:[~2005-01-21 3:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 3:18 Arnaldo Carvalho de Melo [this message]
2005-01-26 6:24 ` [PATCH 0/12] remove sk_protinfo series David S. Miller
2005-02-09 5:04 ` 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=41F07497.4020109@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
/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).