mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: "Michał Winiarski" <michal.winiarski@intel.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Simon Ser <contact@emersion.fr>
Subject: Re: [PATCH v3 0/4] drm: Use full allocated minor range for DRM
Date: Tue, 6 Sep 2022 15:21:25 +0100	[thread overview]
Message-ID: <YxdXZbFBHIevYwRz@casper.infradead.org> (raw)
In-Reply-To: <20220906140117.409852-1-michal.winiarski@intel.com>

On Tue, Sep 06, 2022 at 04:01:13PM +0200, Michał Winiarski wrote:
> 64 DRM device nodes is not enough for everyone.
> Upgrade it to ~512K (which definitely is more than enough).
> 
> To allow testing userspace support for >64 devices, add additional DRM
> modparam (skip_legacy_minors) which causes DRM to skip allocating minors
> in 0-192 range.
> Additionally - one minor tweak around minor DRM IDR locking and IDR lockdep
> annotations.

The IDR is deprecated; rather than making all these changes around
the IDR, could you convert it to use the XArray instead?  I did it
once before, but those patches bounced off the submissions process.


  parent reply	other threads:[~2022-09-06 15:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06 14:01 Michał Winiarski
2022-09-06 14:01 ` [PATCH v3 1/4] drm: Expand max DRM device number to full MINORBITS Michał Winiarski
2022-09-06 14:01 ` [PATCH v3 2/4] drm: Introduce skip_legacy_minors modparam Michał Winiarski
2022-09-06 14:01 ` [PATCH v3 3/4] drm: Use mutex for minors Michał Winiarski
2022-09-06 14:01 ` [PATCH v3 4/4] idr: Add might_alloc() annotation Michał Winiarski
2022-09-06 14:21 ` Matthew Wilcox [this message]
2022-09-06 16:08   ` [PATCH v3 0/4] drm: Use full allocated minor range for DRM Michał Winiarski

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=YxdXZbFBHIevYwRz@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=airlied@linux.ie \
    --cc=contact@emersion.fr \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=michal.winiarski@intel.com \
    --cc=mripard@kernel.org \
    --cc=tzimmermann@suse.de \
    /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®