On Sun, Mar 11, 2018 at 12:16:25PM -0700, Dan Williams wrote:
> I did the rename, and am housing these in fs/dax.c, I assume that's
> what you wanted.
libfs.c would seem ok to, but we're into micro-management land now :)
On Sun, Mar 11, 2018 at 12:16:25PM -0700, Dan Williams wrote:
> I did the rename, and am housing these in fs/dax.c, I assume that's
> what you wanted.
libfs.c would seem ok to, but we're into micro-management land now :)
On Sat, Mar 10, 2018 at 9:40 AM, Dan Williams wrote:
> On Sat, Mar 10, 2018 at 1:46 AM, Christoph Hellwig wrote:
>>> +int dax_set_page_dirty(struct page *page)
>>> +{
>>> + /*
>>> + * Unlike __set_page_dirty_no_writeback that handles dirty page
>>>
On Sat, Mar 10, 2018 at 9:40 AM, Dan Williams wrote:
> On Sat, Mar 10, 2018 at 1:46 AM, Christoph Hellwig wrote:
>>> +int dax_set_page_dirty(struct page *page)
>>> +{
>>> + /*
>>> + * Unlike __set_page_dirty_no_writeback that handles dirty page
>>> + * tracking in the page object,
On Sat, Mar 10, 2018 at 1:46 AM, Christoph Hellwig wrote:
>> +int dax_set_page_dirty(struct page *page)
>> +{
>> + /*
>> + * Unlike __set_page_dirty_no_writeback that handles dirty page
>> + * tracking in the page object, dax does all dirty tracking in
>> + * the
On Sat, Mar 10, 2018 at 1:46 AM, Christoph Hellwig wrote:
>> +int dax_set_page_dirty(struct page *page)
>> +{
>> + /*
>> + * Unlike __set_page_dirty_no_writeback that handles dirty page
>> + * tracking in the page object, dax does all dirty tracking in
>> + * the inode
> +int dax_set_page_dirty(struct page *page)
> +{
> + /*
> + * Unlike __set_page_dirty_no_writeback that handles dirty page
> + * tracking in the page object, dax does all dirty tracking in
> + * the inode address_space in response to mkwrite faults. In the
> + * dax case
> +int dax_set_page_dirty(struct page *page)
> +{
> + /*
> + * Unlike __set_page_dirty_no_writeback that handles dirty page
> + * tracking in the page object, dax does all dirty tracking in
> + * the inode address_space in response to mkwrite faults. In the
> + * dax case
In preparation for the dax implementation to start associating dax pages
to inodes via page->mapping, we need to provide a 'struct
address_space_operations' instance for dax. Otherwise, direct-I/O
triggers incorrect page cache assumptions and warnings like the
following:
WARNING: CPU: 27 PID:
In preparation for the dax implementation to start associating dax pages
to inodes via page->mapping, we need to provide a 'struct
address_space_operations' instance for dax. Otherwise, direct-I/O
triggers incorrect page cache assumptions and warnings like the
following:
WARNING: CPU: 27 PID:
10 matches
Mail list logo