All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: don't return vmalloc() memory from f2fs_kmalloc()
Date: Thu, 4 Jun 2020 21:56:06 -0700	[thread overview]
Message-ID: <20200605045606.GR2667@sol.localdomain> (raw)
In-Reply-To: <20200605011535.GA102178@google.com>

On Thu, Jun 04, 2020 at 06:15:35PM -0700, Jaegeuk Kim wrote:
> > 
> > I went through every remaining caller of f2fs_kmalloc() and f2fs_kzalloc().  I
> > think we're fine, except for possibly the allocation of blkz_seq in
> > init_blkz_info().  How many zones can we expect on a zoned block device?
> 
> In the worst case, it can be 16TB / 2MB = 8M entries.

In that case, I'll make init_blkz_info() use f2fs_kvzalloc() too.

- Eric


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      reply	other threads:[~2020-06-05  4:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-05 20:48 [f2fs-dev] [PATCH] f2fs: don't return vmalloc() memory from f2fs_kmalloc() Eric Biggers
2020-05-06  7:43 ` Chao Yu
2020-05-06 18:43   ` Eric Biggers
2020-05-07  3:13     ` Chao Yu
2020-05-15 19:13 ` Eric Biggers
2020-05-18 18:06 ` Jaegeuk Kim
2020-05-18 18:35   ` Eric Biggers
2020-05-18 19:10     ` Jaegeuk Kim
2020-06-04 21:06       ` Eric Biggers
2020-06-05  1:15         ` Jaegeuk Kim
2020-06-05  4:56           ` Eric Biggers [this message]

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=20200605045606.GR2667@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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.