From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Configuring large numbers of disks
Date: Tue, 11 Oct 2005 18:43:45 +0000 [thread overview]
Message-ID: <20051011184345.GC20751@vrfy.org> (raw)
In-Reply-To: <1128975292.21643.30.camel@markh1.pdx.osdl.net>
On Tue, Oct 11, 2005 at 11:35:29AM -0700, Mark Haverkamp wrote:
> On Tue, 2005-10-11 at 20:25 +0200, Kay Sievers wrote:
> > On Mon, Oct 10, 2005 at 01:14:51PM -0700, Mark Haverkamp wrote:
> > > I have 4000 fibrechannel LUNs connected to my system. There are two
> > > paths to the devices and two ports on the host connected via a switch.
> > > This gives 16000 when probed. All of the devices are being configured
> > > and appear in /sys/block. I have had problems getting all of the
> > > entries in /dev created. I have been able to get udev to create all the
> > > entries in /dev if I recompile udevd to increase the netlink setsockopt
> > > SO_RCVBUF to 16384 * 1024 from the original 1024 * 1024.
> >
> > Did you allow such a big socket buffer? What does:
> > grep . /proc/sys/net/core/*
> > print on that box?
>
> # grep . /proc/sys/net/core/*
> /proc/sys/net/core/dev_weight:64
> /proc/sys/net/core/message_burst:10
> /proc/sys/net/core/message_cost:5
> /proc/sys/net/core/netdev_budget:300
> /proc/sys/net/core/netdev_max_backlog:1000
> /proc/sys/net/core/optmem_max:20480
> /proc/sys/net/core/rmem_default:131072
> /proc/sys/net/core/rmem_max:131071
> /proc/sys/net/core/somaxconn:128
> /proc/sys/net/core/wmem_default:131072
> /proc/sys/net/core/wmem_max:131071
>
> Although before I start udevd I issue sysctl commands to increase the
> maximum buffer sizes.
>
> sysctl -w net.core.rmem_max\x16777216
> sysctl -w net.core.wmem_max\x16777216
I will make udevd to force it itself with the new option, so that will
no longer be needed.
Kay
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2005-10-11 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 20:14 Configuring large numbers of disks Mark Haverkamp
2005-10-11 18:25 ` Kay Sievers
2005-10-11 18:35 ` Mark Haverkamp
2005-10-11 18:43 ` Kay Sievers [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=20051011184345.GC20751@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@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).