From: Al Viro <viro@ZenIV.linux.org.uk>
To: Jerome Glisse <jglisse@redhat.com>
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: Wed, 31 Jan 2018 17:55:58 +0000 [thread overview]
Message-ID: <20180131175558.GA30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20180131174245.GE2912@redhat.com>
On Wed, Jan 31, 2018 at 12:42:45PM -0500, Jerome Glisse wrote:
> For block devices the idea is to use struct page and buffer_head (first one of
> a page) as a key to find mapping (struct address_space) back.
Details, please...
_______________________________________________
Lsf-pc mailing list
Lsf-pc@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/lsf-pc
WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Jerome Glisse <jglisse@redhat.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, linux-block@vger.kernel.org
Subject: Re: [LSF/MM TOPIC] Killing reliance on struct page->mapping
Date: Wed, 31 Jan 2018 17:55:58 +0000 [thread overview]
Message-ID: <20180131175558.GA30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20180131174245.GE2912@redhat.com>
On Wed, Jan 31, 2018 at 12:42:45PM -0500, Jerome Glisse wrote:
> For block devices the idea is to use struct page and buffer_head (first one of
> a page) as a key to find mapping (struct address_space) back.
Details, please...
--
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-01-31 17:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 0:43 [LSF/MM TOPIC] Killing reliance on struct page->mapping Jerome Glisse
2018-01-30 0:43 ` Jerome Glisse
2018-01-30 0:43 ` Jerome Glisse
2018-01-31 16:56 ` Al Viro
2018-01-31 16:56 ` Al Viro
2018-01-31 17:42 ` [Lsf-pc] " Jerome Glisse
2018-01-31 17:42 ` Jerome Glisse
2018-01-31 17:42 ` Jerome Glisse
2018-01-31 17:55 ` Al Viro [this message]
2018-01-31 17:55 ` Al Viro
2018-01-31 18:13 ` [Lsf-pc] " Jerome Glisse
2018-01-31 18:13 ` Jerome Glisse
2018-01-31 18:13 ` Jerome Glisse
2018-02-01 15:34 ` [Lsf-pc] " Jens Axboe
2018-02-01 15:34 ` Jens Axboe
2018-02-01 15:57 ` Jerome Glisse
2018-02-01 15:57 ` Jerome Glisse
2018-02-01 15:57 ` Jerome Glisse
2018-02-01 16:00 ` Jens Axboe
2018-02-01 16:00 ` Jens Axboe
2018-02-01 16:33 ` Jerome Glisse
2018-02-01 16:33 ` Jerome Glisse
2018-02-01 16:33 ` Jerome Glisse
2018-02-01 12:27 ` Kirill A. Shutemov
2018-02-01 12:27 ` Kirill A. Shutemov
2018-02-01 13:22 ` Jerome Glisse
2018-02-01 13:22 ` Jerome Glisse
2018-02-01 13:22 ` Jerome Glisse
2018-01-31 17:09 ` Igor Stoppa
2018-01-31 17:09 ` Igor Stoppa
2018-01-31 17:09 ` Igor Stoppa
2018-01-31 17:48 ` Jerome Glisse
2018-01-31 17:48 ` Jerome Glisse
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=20180131175558.GA30522@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--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 \
/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.