From: Patrick McHardy <kaber@trash.net>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org, James.Bottomley@SteelEye.com,
itn780@yahoo.com, linux-scsi@vger.kernel.org, hch@lst.de,
akpm@osdl.org
Subject: Re: Netlink allocation for iSCSI and others
Date: Mon, 08 Aug 2005 23:19:37 +0200 [thread overview]
Message-ID: <42F7CC69.3060808@trash.net> (raw)
In-Reply-To: <20050808.134731.74751192.davem@davemloft.net>
David S. Miller wrote:
> So we can increase MAX_LINKS to 256 and that's what I think I will do
> for 2.6.14 unless there is a very serious objection. The tables sized
> by MAX_LINKS in af_netlink.c are dynamically allocated, and the only
> linear iterations over MAX_LINKS are for the netlink socket procfs
> seq-file dumper, so it's not a performance issue either.
I think we should increase it when allocating new numbers to save the
unused memory for the larger nltable and additional pid hashes.
Userspace shouldn't care if we change it.
next prev parent reply other threads:[~2005-08-08 21:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 20:47 Netlink allocation for iSCSI and others David S. Miller
2005-08-08 21:19 ` Patrick McHardy [this message]
2005-08-08 21:21 ` 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=42F7CC69.3060808@trash.net \
--to=kaber@trash.net \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=hch@lst.de \
--cc=itn780@yahoo.com \
--cc=linux-scsi@vger.kernel.org \
--cc=netdev@vger.kernel.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).