mmap vs read/write

J

junky_fellow

Consider a scenario, where one process uses mmap() to access/modify
a particaular file and at the same time other process uses read/write
to access/modify the same file.

I wanted to know whether it may cause inconsistency or not?
May be this question is out of context for c.l.c, i would be
grateful if someone help me. Just a hint will do.

thanx and regards......
 
J

Jack Klein

Consider a scenario, where one process uses mmap() to access/modify
a particaular file and at the same time other process uses read/write
to access/modify the same file.

I wanted to know whether it may cause inconsistency or not?
May be this question is out of context for c.l.c, i would be
grateful if someone help me. Just a hint will do.

thanx and regards......

I'm afraid it is off-topic here. C does not have either mmap() or
processes. Both of these are platform specific extensions, not part
of the language. You need to ask in a platform specific support
group, perhaps or
 
B

Ben Pfaff

Consider a scenario, where one process uses mmap() to access/modify
a particaular file and at the same time other process uses read/write
to access/modify the same file.

Your question is outside the domain of comp.lang.c, which discusses
only the standard C programming language, including the standard C
library. This is a remarkably narrow topic compared to what many
people expect.

For your convenience, the list below contains topics that are not
on-topic for comp.lang.c, and suggests newsgroups for you to explore
if you have questions about these topics. Please do observe proper
netiquette before posting to any of these newsgroups. In particular,
you should read the group's charter and FAQ, if any (FAQs are
available from www.faqs.org and other sources). If those fail to
answer your question then you should browse through at least two weeks
of recent articles to make sure that your question has not already
been answered.

* OS-specific questions, such as how to clear the screen,
access the network, list the files in a directory, or read
"piped" output from a subprocess. These questions should be
directed to OS-specific newsgroups, such as
comp.os.ms-windows.programmer.misc, comp.unix.programmer, or
comp.os.linux.development.apps.

* Compiler-specific questions, such as installation issues and
locations of header files. Ask about these in
compiler-specific newsgroups, such as gnu.gcc.help or
comp.os.ms-windows.programmer.misc. Questions about writing
compilers are appropriate in comp.compilers.

* Processor-specific questions, such as questions about
assembly and machine code. x86 questions are appropriate in
comp.lang.asm.x86, embedded system processor questions may
be appropriate in comp.arch.embedded.

* ABI-specific questions, such as how to interface assembly
code to C. These questions are both processor- and
OS-specific and should typically be asked in OS-specific
newsgroups.

* Algorithms, except questions about C implementations of
algorithms. "How do I implement algorithm X in C?" is not a
question about a C implementation of an algorithm, it is a
request for source code. Newsgroups comp.programming and
comp.theory may be appropriate.

* Making C interoperate with other languages. C has no
facilities for such interoperation. These questions should
be directed to system- or compiler-specific newsgroups. C++
has features for interoperating with C, so consider
comp.lang.c++ for such questions.

* The C standard, as opposed to standard C. Questions about
the C standard are best asked in comp.std.c.

* C++. Please do not post or cross-post questions about C++
to comp.lang.c. Ask C++ questions in C++ newsgroups, such
as comp.lang.c++ or comp.lang.c++.moderated.

* Test posts. Please test in a newsgroup meant for testing,
such as alt.test.

news.groups.questions is a good place to ask about the appropriate
newsgroup for a given topic.
 
D

Derk Gwen

(e-mail address removed) (junky_fellow) wrote:
# Consider a scenario, where one process uses mmap() to access/modify
# a particaular file and at the same time other process uses read/write
# to access/modify the same file.

Really depends on the details of the operating system. The answer should be
simple, but so many kernel people have their head up their butt on how
virtual memory should work, that there is no consistent answer.

Multics virtual memory was an improvement on all its successors.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
474,141
Messages
2,570,813
Members
47,357
Latest member
sitele8746

Latest Threads

Top