linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Goldwyn Rodrigues <rgoldwyn@suse.de>
To: lsf-pc@lists.linux-foundation.org,
	Linux FS-devel Mailing List <linux-fsdevel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: [LSF/MM ATTEND] memory allocation scope
Date: Wed, 14 Feb 2018 16:51:53 -0600	[thread overview]
Message-ID: <8b9d4170-bc71-3338-6b46-22130f828adb@suse.de> (raw)


Discussion with the memory folks towards scope based allocation
I am working on converting some of the GFP_NOFS memory allocation calls
to new scope API [1]. While other allocation types (noio, nofs,
noreclaim) are covered. Are there plans for identifying scope of
GFP_ATOMIC allocations? This should cover most (if not all) of the
allocation scope.

Transient Errors with direct I/O
In a large enough direct I/O, bios are split. If any of these bios get
an error, the whole I/O is marked as erroneous. What this means at the
application level is that part of your direct I/O data may be written
while part may not be. In the end, you can have an inconsistent write
with some parts of it written and some not. Currently the applications
need to overwrite the whole write() again.

Other things I am interested in:
 - new mount API
 - Online Filesystem Check
 - FS cache shrinking

[1] https://lwn.net/Articles/710545/


-- 
Goldwyn

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

             reply	other threads:[~2018-02-14 22:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-14 22:51 Goldwyn Rodrigues [this message]
2018-02-15  3:53 ` NeilBrown
2018-02-15 14:19   ` Goldwyn Rodrigues
2018-02-15 14:48 ` Michal Hocko
2018-02-15 15:57   ` [Lsf-pc] " James Bottomley
2018-02-15 16:02     ` Michal Hocko
2018-02-15 16:06       ` Michal Hocko

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=8b9d4170-bc71-3338-6b46-22130f828adb@suse.de \
    --to=rgoldwyn@suse.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.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