It would help if you told us what you were trying to do. What is file descriptor 5 and how was it opened? Also, I doubt '2680' is a multiple of your page size, so you cannot create a 2,680-byte mapping.
I am trying to get oprofile to work. The file I am opening is a sample file. Here is the code for the open:
data->fd =3D open(filename, flags, 0644);
where filename =3D "/var/lib/oprofile/samples//current/{kern}/no-vmlinux/ {dep}/{kern}/no-vmlinux/TIMER.0.0.all.all.all" where flags =3D O_CREAT | O_RDWR
The file /var/lib/oprofile/samples//current/{kern}/no-vmlinux/{dep}/ {kern}/no-vmlinux/TIMER.0.0.all.all.all does exist.
I changed the length to the page size and it made no difference. According to
formatting link
"This can be any length you want. (Aside: if len not a multiple of the virtual memory page size, you will get a blocksize that is rounded up to that size. The extra bytes will be 0, and any changes you make to them will not modify the file.) "
That would do terrible things to the utility of shared memory -- no, MAP_SHARED and PROT_WRITE are compatible. Maybe you're thinking of MAP_SHARED and MAP_ANONYMOUS (which didn't used to be compatible, but is since 2.4).
--
As we enjoy great advantages from the inventions of others, we should
be glad of an opportunity to serve others by any invention of ours;
and this we should do freely and generously. (Benjamin Franklin)
No. It is feasible. The parameter prot determines whether read, write, execute, or some combination of accesses are permitted to the data being mapped. The prot should be either PROT_NONE or the bitwise inclusive OR of one or more of the other flags listed below - PROT_READ Data can be read. PROT_WRITE Data can be written. PROT_EXEC Data can be executed. PROT_NONE Data cannot be accessed.
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.