All of lore.kernel.org
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: akpm@linux-foundation.org
Cc: manfred@colorfullife.com, dave@stgolabs.net,
	linux-kernel@vger.kernel.org
Subject: [PATCH -next 0/4] sysvipc: ipc-key management improvements
Date: Thu, 31 Aug 2017 10:20:45 -0700	[thread overview]
Message-ID: <20170831172049.14576-1-dave@stgolabs.net> (raw)

Hi,

Here are a few improvements I spotted while eyeballing Guillaume's
rhashtable implementation for ipc keys. The first and fourth patches
are the interesting ones, the middle two are trivial.

Applies against today's -next.
Passes ltp ipc related testcases.

Thanks!

Davidlohr Bueso (4):
  sysvipc: unteach ids->next_id for !CHECKPOINT_RESTORE
  sysvipc: duplicate lock comments wrt ipc_addid()
  sysvipc: properly name ipc_addid() limit parameter
  sysvipc: make get_maxid O(1) again

 arch/x86/Kconfig              |  2 +-
 include/linux/ipc_namespace.h |  3 ++
 ipc/sem.c                     |  1 +
 ipc/shm.c                     |  1 +
 ipc/util.c                    | 97 ++++++++++++++++++++++++-------------------
 ipc/util.h                    | 26 ++++++++----
 6 files changed, 79 insertions(+), 51 deletions(-)

-- 
2.12.0

             reply	other threads:[~2017-08-31 17:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-31 17:20 Davidlohr Bueso [this message]
2017-08-31 17:20 ` [PATCH 1/4] sysvipc: unteach ids->next_id for !CHECKPOINT_RESTORE Davidlohr Bueso
2017-10-03 22:03   ` Andrew Morton
2017-08-31 17:20 ` [PATCH 2/4] sysvipc: duplicate lock comments wrt ipc_addid() Davidlohr Bueso
2017-08-31 17:20 ` [PATCH 3/4] sysvipc: properly name ipc_addid() limit parameter Davidlohr Bueso
2017-08-31 17:20 ` [PATCH 4/4] sysvipc: make get_maxid O(1) again Davidlohr Bueso
2017-08-31 17:37   ` Davidlohr Bueso

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=20170831172049.14576-1-dave@stgolabs.net \
    --to=dave@stgolabs.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.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.