From: "David S. Miller" <davem@redhat.com>
To: Sridhar Samudrala <sri@us.ibm.com>
Cc: netdev@oss.sgi.com, lksctp-developers@lists.sourceforge.net
Subject: Re: [BK PATCH] 2.6 SCTP updates
Date: Fri, 13 Feb 2004 21:52:27 -0800 [thread overview]
Message-ID: <20040213215227.270a8147.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0402131443350.2190@localhost.localdomain>
On Fri, 13 Feb 2004 16:07:05 -0800 (PST)
Sridhar Samudrala <sri@us.ibm.com> wrote:
> Please do a
> bk pull http://linux-lksctp.bkbits.net/lksctp-2.5.work
> to get the following fixes to SCTP on top of linux 2.6.2.
I am pulling this, however I strongly disagree with this change:
> # 04/02/12 sri@us.ibm.com 1.1552
> # [SCTP] Use __get_free_pages() to allocate ssnmap.
> #
> # This is needed to avoid kmalloc()'s 128K limit when an association is
> # initialized with a large no. of streams(more than 65000 inbound +
> # outbound streams).
This is madness because it means that every assosciation created eats
at least PAGE_SIZE bytes of memory, even if the ssnmap is tiny.
Maybe you should just brance between two allocation schemes based upon
what sctp_ssnmap_size() returns.
next prev parent reply other threads:[~2004-02-14 5:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 0:07 [BK PATCH] 2.6 SCTP updates Sridhar Samudrala
2004-02-14 5:52 ` David S. Miller [this message]
2004-02-16 5:55 ` Sridhar Samudrala
-- strict thread matches above, loose matches on Subject: below --
2004-07-24 0:18 Sridhar Samudrala
2004-07-25 5:27 ` David S. Miller
2004-07-26 13:51 ` Sridhar Samudrala
2004-04-06 17:28 Sridhar Samudrala
2004-03-23 20:13 Sridhar Samudrala
2004-03-24 20:01 ` David S. Miller
2003-10-02 23:46 Sridhar Samudrala
2003-10-03 9:48 ` 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=20040213215227.270a8147.davem@redhat.com \
--to=davem@redhat.com \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=netdev@oss.sgi.com \
--cc=sri@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.