From: Leon Woestenberg <leon.woestenberg@gmail.com>
To: Adam Turk <bofh1234@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: recommended programming practices for writing (was Linux 2.6.29)
Date: Thu, 26 Mar 2009 20:35:15 +0100 [thread overview]
Message-ID: <c384c5ea0903261235sf1a4440q6fb5f38c983770bc@mail.gmail.com> (raw)
In-Reply-To: <COL112-W81AF4A8C222B9941D8295FC8910@phx.gbl>
Hello Adam,
On Thu, Mar 26, 2009 at 8:03 PM, Adam Turk <bofh1234@hotmail.com> wrote:
>
> I have been reading the Linux 2.6.29 thread with interest. I have written several (10 or so) C programs that write large amounts of data (between 1 and 2 GB file sizes are common). A snippet of code looks like this:
>
> I learned C about 15 years ago and there was no mention of a fsync. My C book doesn't mention fsync either. Granted I have written only 25-30 applications in the last 15 years or so so I am not an expert C programmer.
>
Your question is really off-topic for the Linux Kernel mailing list,
but let me point you somewhere else:
There is (1) the C library and (2) the functions provided by your
operating system. Linux follows to some extend the POSIX functions for
(2).
A good read is the book "Linux Systems Programming" if you want to go
beyond what the C library offers, for starters.
Regards,
--
Leon
next prev parent reply other threads:[~2009-03-26 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 19:03 Adam Turk
2009-03-26 19:34 ` Bernd Petrovitsch
2009-03-26 22:33 ` Adam Turk
2009-03-26 19:35 ` Leon Woestenberg [this message]
2009-03-26 22:32 ` Adam Turk
2009-03-26 22:40 ` J.A. Magallón
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c384c5ea0903261235sf1a4440q6fb5f38c983770bc@mail.gmail.com \
--to=leon.woestenberg@gmail.com \
--cc=bofh1234@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®