[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fuse-devel
Subject:    [fuse-devel] direct_io vs sys_execve
From:       Francois THIEBOLT <thiebolt () irit ! fr>
Date:       2007-01-30 9:30:19
Message-ID: 45BF102B.9090506 () irit ! fr
[Download RAW message or body]

Dear,

I understand that in order to get an application executed, the kernel 
need to mmap the code in page cache to then map it into the newly 
created address space ... which means no -odirect_io fuse main option.

Nevertheless, i'd like to know if there's a way to distinguish between 
an application openening a file and an open request from sys_execve 
internals ... maybe fuse_get_context->pid ?

With such a feature, it'll be possible to disengage direct_io on an open 
file basis ( direct_io flag) only when it is related to sys_execve ...

François.

-- 
-------------------------------------------------------------
THIEBOLT Francois \ You think your computer runs too slow ?
UPS Toulouse III  \ - Check if nobody's asked for tea !
thiebolt@irit.fr  \ "The Hitchhiker's Guide to the Galaxy" D.Adams


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
fuse-devel mailing list
fuse-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fuse-devel


[prev in list] [next in list] [prev in thread] [next in thread]