From: Gao Xiang via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Jaegeuk Kim <jaegeuk@kernel.org>
Subject: Re: [f2fs-dev] [PATCH] f2fs: bio_alloc should never fail
Date: Wed, 30 Oct 2019 23:50:37 +0800 [thread overview]
Message-ID: <20191030155020.GA3953@hsiangkao-HP-ZHAN-66-Pro-G1> (raw)
In-Reply-To: <20191030151444.GC16197@mit.edu>
Hi Ted,
On Wed, Oct 30, 2019 at 11:14:45AM -0400, Theodore Y. Ts'o wrote:
> On Wed, Oct 30, 2019 at 06:43:45PM +0800, Gao Xiang wrote:
> > > You're right, in low memory scenario, allocation with bioset will be faster, as
> > > you mentioned offline, maybe we can add/use a priviate bioset like btrfs did
> > > rather than using global one, however, we'd better check how deadlock happen
> > > with a bioset mempool first ...
> >
> > Okay, hope to get hints from Jaegeuk and redo this patch then...
>
> It's not at all clear to me that using a private bioset is a good idea
> for f2fs. That just means you're allocating a separate chunk of
> memory just for f2fs, as opposed to using the global pool. That's an
> additional chunk of non-swapable kernel memory that's not going to be
> available, in *addition* to the global mempool.
>
> Also, who else would you be contending for space with the global
> mempool? It's not like an mobile handset is going to have other users
> of the global bio mempool.
>
> On a low-end mobile handset, memory is at a premium, so wasting memory
> to no good effect isn't going to be a great idea.
Thanks for your reply. I agree with your idea.
Actually I think after this version patch is applied, all are the same
as the previous status (whether some deadlock or not).
So I'm curious about the original issue in commit 740432f83560
("f2fs: handle failed bio allocation"). Since f2fs manages multiple write
bios with its internal fio but it seems the commit is not helpful to
resolve potential mempool deadlock (I'm confused since no calltrace,
maybe I'm wrong)...
I think it should be gotten clear first and think how to do next..
(I tend not to add another private bioset since it's unshareable as you
said as well...)
Thanks,
Gao Xiang
>
> Regards,
>
> - Ted
>
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2019-10-30 15:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 3:55 [f2fs-dev] [PATCH] f2fs: bio_alloc should never fail Gao Xiang
2019-10-30 8:56 ` Chao Yu
2019-10-30 9:15 ` Gao Xiang
2019-10-30 9:27 ` Chao Yu
2019-10-30 10:43 ` Gao Xiang
2019-10-30 15:14 ` Theodore Y. Ts'o
2019-10-30 15:50 ` Gao Xiang via Linux-f2fs-devel [this message]
2019-10-30 16:22 ` Theodore Y. Ts'o
2019-10-30 16:33 ` Jaegeuk Kim
2019-10-30 16:52 ` Gao Xiang via Linux-f2fs-devel
2019-10-31 6:55 ` Chao Yu
2019-10-31 2:03 ` Chao Yu
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=20191030155020.GA3953@hsiangkao-HP-ZHAN-66-Pro-G1 \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=corbet@lwn.net \
--cc=hsiangkao@aol.com \
--cc=jaegeuk@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).