From: Jens Axboe <axboe@kernel.dk>
To: Jerome Glisse <jglisse@redhat.com>, Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
lsf-pc@lists.linux-foundation.org, linux-block@vger.kernel.org
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] Killing reliance on struct page->mapping
Date: Thu, 1 Feb 2018 08:34:58 -0700 [thread overview]
Message-ID: <35c2908e-b6ba-fc29-0a3c-15cb8cf00256@kernel.dk> (raw)
In-Reply-To: <20180131181356.GG2912@redhat.com>
On 1/31/18 11:13 AM, Jerome Glisse wrote:
> That's one solution, another one is to have struct bio_vec store
> buffer_head pointer and not page pointer, from buffer_head you can
> find struct page and using buffer_head and struct page pointer you
> can walk the KSM rmap_item chain to find back the mapping. This
> would be needed on I/O error for pending writeback of a newly write
> protected page, so one can argue that the overhead of the chain lookup
> to find back the mapping against which to report IO error, is an
> acceptable cost.
Ehm nope. bio_vec is a generic container for pages, requiring
buffer_heads to be able to do IO would be insanity.
--
Jens Axboe
--
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>
next prev parent reply other threads:[~2018-02-01 15:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 0:43 Jerome Glisse
2018-01-31 16:56 ` Al Viro
2018-01-31 17:42 ` Jerome Glisse
2018-01-31 17:55 ` Al Viro
2018-01-31 18:13 ` Jerome Glisse
2018-02-01 15:34 ` Jens Axboe [this message]
2018-02-01 15:57 ` [Lsf-pc] " Jerome Glisse
2018-02-01 16:00 ` Jens Axboe
2018-02-01 16:33 ` Jerome Glisse
2018-02-01 12:27 ` Kirill A. Shutemov
2018-02-01 13:22 ` Jerome Glisse
2018-01-31 17:09 ` Igor Stoppa
2018-01-31 17:48 ` Jerome Glisse
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=35c2908e-b6ba-fc29-0a3c-15cb8cf00256@kernel.dk \
--to=axboe@kernel.dk \
--cc=jglisse@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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