unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: 55707@debbugs.gnu.org, 55488@debbugs.gnu.org
Subject: bug#55488: bug#55707: syslogd logging kernel messages slowly?
Date: Sat, 04 Jun 2022 19:35:42 +0200	[thread overview]
Message-ID: <874k10fi1d.fsf_-_@gnu.org> (raw)
In-Reply-To: <878rqcfjcn.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sat, 04 Jun 2022 19:07:20 +0200")

Ludovic Courtès <ludo@gnu.org> skribis:

>   1. Use ‘fdatasync’ rather than ‘fsync’;

Turns out ‘fdatasync’ is about as expensive:

--8<---------------cut here---------------start------------->8---
   1234:301   19:22:00 fdatasync(6)             = 0 <0.398749>
   1236:301   19:22:01 fdatasync(5)             = 0 <0.198520>
   1243:301   19:22:01 fdatasync(6)             = 0 <0.231935>
   1245:301   19:22:01 fdatasync(5)             = 0 <0.183503>
   1252:301   19:22:01 fdatasync(6)             = 0 <0.230854>
   1254:301   19:22:02 fdatasync(5)             = 0 <0.248839>
   1261:301   19:22:02 fdatasync(6)             = 0 <0.181513>
   1263:301   19:22:02 fdatasync(5)             = 0 <0.141267>
   1270:301   19:22:02 fdatasync(6)             = 0 <0.131548>
   1272:301   19:22:02 fdatasync(5)             = 0 <0.124369>
   1279:301   19:22:02 fdatasync(6)             = 0 <0.121414>
--8<---------------cut here---------------end--------------->8---

Tested with:

--8<---------------cut here---------------start------------->8---
(define inetutils/fdatasync
  (package/inherit inetutils
    (version (string-append (package-version inetutils) ".fdatasync"))
    (source (origin
              (inherit (package-source inetutils))
              (modules '((guix build utils)))
              (snippet
               '(substitute* "src/syslogd.c"
                  (("fsync") "fdatasync")))))))
--8<---------------cut here---------------end--------------->8---

It still makes more sense than ‘fsync’ though.

Ludo’.




  reply	other threads:[~2022-06-04 17:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 18:49 bug#55488: GDM, GNOME: Can't start desktop session after upgrade Luis Felipe via Bug reports for GNU Guix
2022-05-18  8:44 ` Ludovic Courtès
2022-05-18 14:33   ` Luis Felipe via Bug reports for GNU Guix
2022-05-31  9:29     ` Ludovic Courtès
2022-05-31 20:50       ` Luis Felipe via Bug reports for GNU Guix
2022-06-01 19:55         ` Ludovic Courtès
2022-06-02 19:44           ` Luis Felipe via Bug reports for GNU Guix
2022-06-02 21:02             ` Ludovic Courtès
2022-06-02 23:51               ` bug#55707: " Luis Felipe via Bug reports for GNU Guix
2022-06-03 22:54                 ` Ludovic Courtès
2022-06-04 17:07                   ` Ludovic Courtès
2022-06-04 17:35                     ` Ludovic Courtès [this message]
2022-06-04 19:30                     ` bug#55488: bug#55707: syslogd logging kernel messages slowly? Ludovic Courtès
2022-06-05 15:25                       ` Luis Felipe via Bug reports for GNU Guix
2022-06-06 10:00                         ` Ludovic Courtès
2022-06-06 16:31                           ` Luis Felipe via Bug reports for GNU Guix
2022-06-06 20:46                             ` Ludovic Courtès
2022-06-05 13:19                   ` bug#55488: GDM, GNOME: Can't start desktop session after upgrade Luis Felipe via Bug reports for GNU Guix
2022-06-06 18:11                     ` Luis Felipe via Bug reports for GNU Guix
2022-06-06 20:50                       ` bug#55488: bug#55707: syslogd logging kernel messages slowly? Ludovic Courtès
2022-06-06 23:09 ` bug#55488: GDM, GNOME: Can't start desktop session after upgrade Luis Felipe via Bug reports for GNU Guix
2022-06-06 23:11 ` Luis Felipe via Bug reports for GNU Guix

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874k10fi1d.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=55488@debbugs.gnu.org \
    --cc=55707@debbugs.gnu.org \
    --cc=luis.felipe.la@protonmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).