mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@davemloft.net>
To: dmitry_yus@yahoo.com
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, 30 Jul 2005 17:33:52 -0700 (PDT)	[thread overview]
Message-ID: <20050730.173352.41656851.davem@davemloft.net> (raw)
In-Reply-To: <1122758728.13559.4.camel@mylaptop>

From: Dmitry Yusupov <dmitry_yus@yahoo.com>
Date: Sat, 30 Jul 2005 14:25:28 -0700

> It would be nice to set MAX_LINKS to 64 and close this issue for now,

James and Dmitry, increasing MAX_LINKS does't work, did you actually
try to open a netlink socket with a protocol number larger than 32?

It will not work.  Don't you think I'd implement such a simple fix to
expand the protocol number space if it was that easy? :-)

You can't increase MAX_LINKS past 32 because this is also the value of
NPROTO.  It is impossible to create a new socket with a protocol value
larger than NPROTO, and this value is exported into userspace as well.

  reply	other threads:[~2005-07-31  0:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01 20:08 Alex Aizman
2005-06-01 20:54 ` Patrick McFarland
2005-06-01 21:08   ` 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 [this message]
2005-08-02 17:18         ` Mike Christie
2005-07-31  0:34       ` David S. Miller
2005-08-06 20:46         ` Patrick McHardy

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=20050730.173352.41656851.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=James.Bottomley@SteelEye.com \
    --cc=dmitry_yus@yahoo.com \
    --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

all inboxes | Powered by JetHome®