Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [PATCH] brd: expose number of allocated pages in debugfs
To:     Saravanan D <saravanand@fb.com>, linux-block@vger.kernel.org,
        linux-kernel@vger.kernel.org
Cc:     jkkm@fb.com, tj@kernel.org, kernel-team@fb.com,
        Calvin Owens <calvinowens@fb.com>
References: <20210416211829.4002947-1-saravanand@fb.com>
From:   Jens Axboe <axboe@kernel.dk>
Message-ID: <cd3added-1674-165a-0cfd-5e5841b738c7@kernel.dk>
Date:   Wed, 21 Apr 2021 10:56:12 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <20210416211829.4002947-1-saravanand@fb.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Precedence: bulk

On 4/16/21 3:18 PM, Saravanan D wrote:
> From: Calvin Owens <calvinowens@fb.com>
> 
> While the maximum size of each ramdisk is defined either
> as a module parameter, or compile time default, it's impossible
> to know how many pages have currently been allocated by each
> ram%d device, since they're allocated when used and never freed.
> 
> This patch creates a new directory at this location:
> 
> »       /sys/kernel/debug/ramdisk_pages/
> 
> ...which will contain a file named "ram%d" for each instantiated
> ramdisk on the system. The file is read-only, and read() will
> output the number of pages currently held by that ramdisk.

I folded in the justification and applied it for 5.13, thanks.

-- 
Jens Axboe