linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
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>
Subject: Re: [PATCH] brd: expose number of allocated pages in debugfs
Date: Wed, 21 Apr 2021 10:56:12 -0600	[thread overview]
Message-ID: <cd3added-1674-165a-0cfd-5e5841b738c7@kernel.dk> (raw)
In-Reply-To: <20210416211829.4002947-1-saravanand@fb.com>

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


  parent reply	other threads:[~2021-04-21 16:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 21:18 [PATCH] brd: expose number of allocated pages in debugfs Saravanan D
2021-04-20 22:29 ` Saravanan D
2021-04-21 16:56 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-08-26 15:20 Kyle McMartin

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=cd3added-1674-165a-0cfd-5e5841b738c7@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=calvinowens@fb.com \
    --cc=jkkm@fb.com \
    --cc=kernel-team@fb.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=saravanand@fb.com \
    --cc=tj@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).