Re: Should implementations of ->direct_access be allowed to sleep?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 03/29/2015 11:02 AM, Boaz Harrosh wrote:
> On 03/26/2015 09:32 PM, Dave Chinner wrote:
<>
> I think that ->direct_access should not be any different then
> any other block-device access, ie allow to sleep.
> 

BTW: Matthew you yourself have said that after a page-load of memcpy
a user should call sched otherwise bad things will happen to the system
you even commented so on one of my patches when you thought I was
allowing a single memcpy bigger than a page.

So if the user *must* call sched after a call to ->direct_access that
is a "sleep" No?

Thanks
Boaz

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




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]