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

List:       helix-datatype-dev
Subject:    RE: [datatype-dev] CR: Change open to open64 to support opening
From:       "Zheng, Huan" <huan.zheng () intel ! com>
Date:       2008-03-27 2:10:33
Message-ID: EFE0C8A50A5D94448E3C7DD762E4FAA20164250D () pdsmsx413 ! ccr ! corp ! intel ! com
[Download RAW message or body]

Hi, Eric
The file I changed is under platform/unix folder, so it is only unix related.
Return type of open64 is int, it is of the same type as m_nFD.

I have compiled and tested with a 2G file, open64 could open it while open report an error.

Best Regards, Zheng, Huan(ZBT)
OTC/SSD/SSG
Intel Aisa-Pacific Research & Developement Ltd
Tel: 021-6116 6435
Inet: 8821 6435
Cub: 3W035

-----Original Message-----
From: Eric Hyche [mailto:ehyche@real.com] 
Sent: 2008Äê3Ô 27ÈÕ 0:15
To: Zheng, Huan; datatype-dev@helixcommunity.org
Cc: Shen, Cathy; helix-client-dev@helixcommunity.org
Subject: RE: [datatype-dev] CR: Change open to open64 to support opening largefile


[For future reference: this should have been submitted to common-dev rather
than datatype-dev. Note that the file you are changing
is in /cvsroot/common, so that means it comes from the
common project. So therefore the proper mailing list
is common-dev. Don't worry about re-submitting this
CR - this is just for CR's in the future...]

Is open64() supported on all systems that open() is? Are
there any semantic differences in how you have to 
treat the file handle m_nFD if you open it with open64().
rather than open()?

Eric

=============================================
Eric Hyche (ehyche@real.com)
Technical Lead
RealNetworks, Inc.  

> -----Original Message-----
> From: datatype-dev-bounces@helixcommunity.org 
> [mailto:datatype-dev-bounces@helixcommunity.org] On Behalf Of 
> Zheng, Huan
> Sent: Wednesday, March 26, 2008 3:22 AM
> To: datatype-dev@helixcommunity.org
> Cc: Shen, Cathy; helix-client-dev@helixcommunity.org; Zheng, Huan
> Subject: [datatype-dev] CR: Change open to open64 to support 
> opening largefile
> 
> Modified by: <huan.zheng@intel.com>
> 
> Date: <03:26:08>
> 
> Project: [Datatype-dev] CR: Change open to open64 to support 
> large file (bigger than 2GB)
> 
> Synopsis:
> 
> Currently fileio does not support large file open
> 
> Overview: 
> 
> In order to open large file(bigger than 2GB), suggest change 
> open to open64.
> 
> Files Added:                                    
> 
>     None
> 
> Files Modified:
> 
>     mmapdatf.cpp (common/fileio/platform/mmapdatf.cpp)
> 
> Image Size and Heap Use impact (Client -Only):
> 
>     little
> 
> Platforms and Profiles Affected:
> 
>     platform:   linux-2.2-libc6-gcc32-i586
> 
>     profile:    helix-client-all-defines
> 
> Distribution Libraries Affected:
> 
>     <smplfsys.so>
> 
> Distribution library impact and planned action:
> 
>     <None>
> 
> Platforms and Profiles Build Verified:
> 
>     Set BIF branch  -> hxclient_3_1_0_atlas_restricted
> 
>     Set Target(s)   -> filesystem
> 
>     Set Profile     -> helix-client-all-defines
> 
>     System ID       -> linux-2.2-libc6-gcc32-i586
> 
> Branch: 
> 
>     HEAD, hxclient_3_1_0_atlas
> 
> Copyright assignment: <MUST be one of the following statements >
> 
>   2.      Intel has signed and delivered a Joint Copyright Assignment
> 
>            to RealNetworks, and received acknowledgment that the 
> 
>            agreement was received. 
> 
> Files Attached:
> 
> fileio.diff
> 
>  
> 
>  
> 
> Best Regards, Zheng, Huan(ZBT)
> 
> OTC/SSD/SSG
> 
> Intel Aisa-Pacific Research & Developement Ltd
> 
> Tel: 021-6116 6435
> 
> Inet: 8821 6435
> 
> Cub: 3W035
> 
>  
> 
> 


_______________________________________________
Datatype-dev mailing list
Datatype-dev@helixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/datatype-dev

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