From: Patrick McHardy <kaber@trash.net>
To: "David S. Miller" <davem@davemloft.net>
Cc: James.Bottomley@SteelEye.com, itn780@yahoo.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
hch@lst.de
Subject: Re: [ANNOUNCE 0/7] Open-iSCSI/Linux-iSCSI-5 High-Performance Initiator
Date: Sat, 06 Aug 2005 22:46:53 +0200 [thread overview]
Message-ID: <42F521BD.9020607@trash.net> (raw)
In-Reply-To: <20050730.173453.130210989.davem@davemloft.net>
David S. Miller wrote:
> From: James Bottomley <James.Bottomley@SteelEye.com>
> Date: Sat, 30 Jul 2005 15:23:20 -0500
>
>>Actually, I saw this and increased MAX_LINKS as well.
>
> That does absolutely nothing, you cannot create sockets
> with protocol numbers larger than NPROTOS which like MAX_LINKS
> has the value 32. And NPROTOS is something we cannot change.
I couldn't find any relationship between MAX_LINKS and NPROTO. NPROTO is
the maximum number of protocol families, the only limitation for
MAX_LINKS seems to be the size of sk_protocol which is an unsigned char.
So I think we can safely increase it.
prev parent reply other threads:[~2005-08-06 20:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 20:08 [ANNOUNCE 0/7] Open-iSCSI/Linux-iSCSI-5 High-Performance Initiator Alex Aizman
2005-06-01 20:54 ` Patrick McFarland
2005-06-01 21:08 ` Alex Aizman
2005-06-01 22:45 ` Christian Iversen
2005-06-02 5:32 ` Alex Aizman
2005-06-01 21:10 ` Ming Zhang
2005-07-30 17:32 ` James Bottomley
2005-07-30 18:36 ` Alex Aizman
2005-07-30 18:38 ` Christoph Hellwig
2005-07-30 19:53 ` David S. Miller
2005-07-30 19:53 ` David S. Miller
2005-07-30 20:23 ` James Bottomley
2005-07-30 21:25 ` Dmitry Yusupov
2005-07-31 0:33 ` David S. Miller
2005-08-02 17:18 ` Mike Christie
2005-07-31 0:34 ` David S. Miller
2005-08-06 20:46 ` Patrick McHardy [this message]
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=42F521BD.9020607@trash.net \
--to=kaber@trash.net \
--cc=James.Bottomley@SteelEye.com \
--cc=davem@davemloft.net \
--cc=hch@lst.de \
--cc=itn780@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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).