[lkml]   [2004]   [Dec]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm2-V0.7.30-2

On Wed, 1 Dec 2004, Ingo Molnar wrote:

> * Paul Davis <> wrote:
> > >also, the problem is that jackd uses _named_ fifos, which are tied to
> > >the raw FS and might trigger journalling activities. Normal pipes
> > >(unnamed fifos) would not cause such problems. Would it be possible to
> > >change jackd to use a pair of pipes, instead of a fifo?
> >
> > i.e. pipe(2) rather than mkfifo(2) ?
> >
> > it would be a complete pain because the pipes have to be
> > "discoverable" across processes. we would have to do fd passing, which
> > is still really quite ugly in linux (and other *nix systems). it would
> > quite difficult, though not impossible.
> yeah. And i think mkfifo(2) objects ought to behave atomically as well,
> it's an unfortunate side-effect of atime/mtime inode semantics that they
> can block.
> your point is correct, the best way to have a system-wide namespace for
> synchronization objects is ... the filesystem hierarchy. If you create a
> unix domain socket then you can distribute your pipe fds, but that's
> indeed somewhat painful.

Don't worry about setting up the stuff. Once you have the pipe it ought to
be RT in the usage of read/write, but setting it up is something you is
something you do "under boot", just as allocating memory and other
non-real-time stuff.

> Ingo


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:08    [W:0.484 / U:2.856 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site