On Tue, May 12, 2015 at 3:24 PM, Christoph Hellwig wrote:
> On Mon, May 11, 2015 at 09:02:54PM +0800, Ming Lei wrote:
>> > But those would be user pages. Anyone who passes a kernel page doesn't
>>
>> Inside kernel it is hard to say one page in page cache is kernel or
>> user page, :-)
>
> Inside
On Mon, May 11, 2015 at 09:02:54PM +0800, Ming Lei wrote:
> > But those would be user pages. Anyone who passes a kernel page doesn't
>
> Inside kernel it is hard to say one page in page cache is kernel or
> user page, :-)
Inside the kernel it's easy to say that it's the caller business to
make
On Mon, May 11, 2015 at 09:02:54PM +0800, Ming Lei wrote:
But those would be user pages. Anyone who passes a kernel page doesn't
Inside kernel it is hard to say one page in page cache is kernel or
user page, :-)
Inside the kernel it's easy to say that it's the caller business to
make sure
On Tue, May 12, 2015 at 3:24 PM, Christoph Hellwig h...@infradead.org wrote:
On Mon, May 11, 2015 at 09:02:54PM +0800, Ming Lei wrote:
But those would be user pages. Anyone who passes a kernel page doesn't
Inside kernel it is hard to say one page in page cache is kernel or
user page, :-)
On Mon, May 11, 2015 at 3:19 PM, Christoph Hellwig wrote:
> On Thu, May 07, 2015 at 08:12:31PM +0800, Ming Lei wrote:
>> In case of loop, it is quite specific about dirtying READ pages in
>> direct IO because fs over loop has considered dirtying these pages
>> already.
>>
>> For other cases of
On Thu, May 07, 2015 at 08:12:31PM +0800, Ming Lei wrote:
> In case of loop, it is quite specific about dirtying READ pages in
> direct IO because fs over loop has considered dirtying these pages
> already.
>
> For other cases of ITER_BVEC or ITER_KVEC, if the page is
> anonymous or mapped,
On Thu, May 07, 2015 at 08:12:31PM +0800, Ming Lei wrote:
In case of loop, it is quite specific about dirtying READ pages in
direct IO because fs over loop has considered dirtying these pages
already.
For other cases of ITER_BVEC or ITER_KVEC, if the page is
anonymous or mapped, dirtying is
On Mon, May 11, 2015 at 3:19 PM, Christoph Hellwig h...@infradead.org wrote:
On Thu, May 07, 2015 at 08:12:31PM +0800, Ming Lei wrote:
In case of loop, it is quite specific about dirtying READ pages in
direct IO because fs over loop has considered dirtying these pages
already.
For other
On Thu, May 7, 2015 at 3:16 PM, Christoph Hellwig wrote:
> On Thu, May 07, 2015 at 01:08:23AM +0800, Ming Lei wrote:
>> When direct IO is submitted from kernel, it is often unnecessary
>> to dirty pages, for example of loop, dirtying pages have been
>> considered in the upper filesystem(over
On Thu, May 07, 2015 at 01:08:23AM +0800, Ming Lei wrote:
> When direct IO is submitted from kernel, it is often unnecessary
> to dirty pages, for example of loop, dirtying pages have been
> considered in the upper filesystem(over loop) side already, and
> they don't need to be dirtied again.
>
>
On Thu, May 07, 2015 at 01:08:23AM +0800, Ming Lei wrote:
When direct IO is submitted from kernel, it is often unnecessary
to dirty pages, for example of loop, dirtying pages have been
considered in the upper filesystem(over loop) side already, and
they don't need to be dirtied again.
So
On Thu, May 7, 2015 at 3:16 PM, Christoph Hellwig h...@infradead.org wrote:
On Thu, May 07, 2015 at 01:08:23AM +0800, Ming Lei wrote:
When direct IO is submitted from kernel, it is often unnecessary
to dirty pages, for example of loop, dirtying pages have been
considered in the upper
When direct IO is submitted from kernel, it is often unnecessary
to dirty pages, for example of loop, dirtying pages have been
considered in the upper filesystem(over loop) side already, and
they don't need to be dirtied again.
So this patch introduces IOCB_DONT_DIRTY_PAGE flag for direct IO,
and
When direct IO is submitted from kernel, it is often unnecessary
to dirty pages, for example of loop, dirtying pages have been
considered in the upper filesystem(over loop) side already, and
they don't need to be dirtied again.
So this patch introduces IOCB_DONT_DIRTY_PAGE flag for direct IO,
and
14 matches
Mail list logo
