From: "David S. Miller" <davem@davemloft.net>
To: jakub@redhat.com
Cc: drepper@redhat.com, davem@redhat.com, libc-hacker@sources.redhat.com
Subject: Re: [PATCH] Assorted SPARC fixes
Date: Mon, 09 Jan 2006 20:36:00 -0000 [thread overview]
Message-ID: <20060109.123651.91447547.davem@davemloft.net> (raw)
In-Reply-To: <20060109145037.GW4625@sunsite.mff.cuni.cz>
From: Jakub Jelinek <jakub@redhat.com>
Date: Mon, 9 Jan 2006 15:50:37 +0100
> tst-cancelx{4,5} (cancellation for pause failed, no idea what's
> going up yet) and tst-cancelx21 (haven't looked)),
The cancelation tests usually fail because they don't use a large
enough pipe write buffer to block with 2.6.x kernels.
It has been suggested in the past to convert these tests to use
AF_UNIX sockets with a reduced socket send buffer setting in order to
get a guarenteed block.
I think this should explain tst-cancelx{4,5} but not tst-cancelx21
next prev parent reply other threads:[~2006-01-09 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 14:50 Jakub Jelinek
2006-01-09 19:50 ` Ulrich Drepper
2006-01-09 20:52 ` Jakub Jelinek
2006-01-09 21:16 ` Ulrich Drepper
2006-01-09 20:36 ` David S. Miller [this message]
2006-01-09 20:55 ` Jakub Jelinek
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=20060109.123651.91447547.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=davem@redhat.com \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.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.
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).