Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1165515
| From | Michal Hocko <mhocko@suse.cz> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] jbd2: get rid of open coded allocation retry loop |
| Date | 2015-06-15 22:00 +0200 |
| Message-ID | <pBII2-4VF-13@gated-at.bofh.it> (permalink) |
| References | <pBDp0-5LO-19@gated-at.bofh.it> <pBIym-4Ka-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon 15-06-15 15:47:04, Theodore Ts'o wrote: > On Mon, Jun 15, 2015 at 04:17:34PM +0200, Michal Hocko wrote: > > insert_revoke_hash does an open coded endless allocation loop if > > journal_oom_retry is true. It doesn't implement any allocation fallback > > strategy between the retries, though. The memory allocator doesn't know > > about the never fail requirement so it cannot potentially help to move > > on with the allocation (e.g. use memory reserves). > > > > Get rid of the retry loop and use __GFP_NOFAIL instead. We will lose the > > debugging message but I am not sure it is anyhow helpful. > > > > Do the same for journal_alloc_journal_head which is doing a similar > > thing. > > > > Signed-off-by: Michal Hocko <mhocko@suse.cz> > > Thanks, applied. Thanks! -- Michal Hocko SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH] jbd2: get rid of open coded allocation retry loop Theodore Ts'o <tytso@mit.edu> - 2015-06-15 21:50 +0200 Re: [PATCH] jbd2: get rid of open coded allocation retry loop Michal Hocko <mhocko@suse.cz> - 2015-06-15 22:00 +0200
csiph-web