git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Trace into open fd and refactor tracing code.

From
Linus Torvalds <torvalds@osdl.org>
Date
Aug 31, 2006, 21:49 UTC
Message-ID
<Pine.LNX.4.64.0608311444200.27779@g5.osdl.org>
In-Reply-To
<7vsljc8udx.fsf@assigned-by-dhcp.cox.net>
On Thu, 31 Aug 2006, Junio C Hamano wrote:
> 
> Actually it was me who suggested the use of fd directly, along
> with trying to do one message in a single write (i.e. not doing
> stdio as much as possible).
I definitely agree with the "one message in a single write" thing.

That's in fact required to make sure that O_APPEND works properly (ie that you don't have potentially different processes mixing output)

> I somehow felt there would be less interference between writes
> issued by process A and process B, but probably I am mistaken.

The atomicity guarantees are the same regardless of whether you do a separate open(), the only thing that matters is that you do want to try to do messages with a single "write()" call, and that you use O_APPEND. That should guarantee that you get good behaviour.

Without O_APPEND, you would obviously have to share one single file descriptor, because otherwise people will just be writing all over each other.

			Linus
Previous: Junio C Hamano
Message 4 of 4 in “Trace into open fd and refactor tracing code.”
  1. Trace into open fd and refactor tracing code.Christian Couder, Aug 31, 2006
  2. Linus TorvaldsAug 31, 2006
  3. Junio C HamanoAug 31, 2006
  4. Linus TorvaldsAug 31, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.