All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nadia Derbey <Nadia.Derbey@bull.net>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Solofo.Ramangalahy@bull.net, linux-kernel@vger.kernel.org,
	Matt Helsley <matthltc@us.ibm.com>, Mingming Cao <cmm@us.ibm.com>,
	Yasunori Goto <y-goto@jp.fujitsu.com>
Subject: Re: [RFC -mm 0/6] sysv ipc: scale msgmnb with the number of cpus
Date: Wed, 25 Jun 2008 12:12:17 +0200	[thread overview]
Message-ID: <48621A01.8090803@bull.net> (raw)
In-Reply-To: <48613635.70103@colorfullife.com>

Manfred Spraul wrote:
> Solofo.Ramangalahy@bull.net wrote:
> 
>> Humm... now this make me think that you did not change the MSGMNB
>> value when you changed MSGMNI and MSGMAX.
>> Maybe that was on purpose?
>>
>>   
> 
> I was afraid that it might break user space applications that queue a 
> few kb of messages.
> That's also the reason for
> 
>>                 if (msgsz + msq->q_cbytes <= msq->q_qbytes &&
>>                                 1 + msq->q_qnum <= msq->q_qbytes) {
>>                         break;
>>                 }
> 
> It's possible to send 0-byte messages even if the  message queue is full 
> [except that you can't send more than MSGMNB messages].
> 

Manfred,

If I'm not missign anything when reading the code, sending up to MSGMNB 
0-bytes messages would make us enqueue MSGMNB msg_msg structures (this 
is in the worst case where no receiver is waiting for those messages).
==> MSGMNB * 24 bytes (or 48 bytes in 64-bit mode))
==> 384 KB with current MSGMNB value (16K).

But 1,5 MB with a MSGMNB=64K

Even if it is a worst case, it should be considered and may be we should 
refine the formula Solofo has proposed if you think this is not a 
reasonable value.
May be add a dependency on the memory size?

Regards,
Nadia

  parent reply	other threads:[~2008-06-25 10:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080605145712.116223941@bull.net>
2008-06-07 14:38 ` [RFC -mm 0/6] sysv ipc: scale msgmnb with the number of cpus Manfred Spraul
2008-06-08  7:19   ` Solofo.Ramangalahy
2008-06-23 13:15   ` Solofo.Ramangalahy
2008-06-24 18:00     ` Manfred Spraul
2008-06-25  6:18       ` Solofo.Ramangalahy
2008-06-25 10:12       ` Nadia Derbey [this message]
2008-06-06  6:09 Solofo.Ramangalahy
2008-06-06  8:23 ` Nick Piggin
2008-06-06 10:20   ` Solofo.Ramangalahy
2008-06-10  6:56 ` Nadia Derbey

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=48621A01.8090803@bull.net \
    --to=nadia.derbey@bull.net \
    --cc=Solofo.Ramangalahy@bull.net \
    --cc=cmm@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=matthltc@us.ibm.com \
    --cc=y-goto@jp.fujitsu.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.