Bug#360292: dvbstream: uses poll() 1500 times/s [patch]

Package: dvbstream
Version: 0.5-2

Whilst looking at a kernel memory leak, I found out that dvbstream is
calling poll() ~ 1500 times a second on my machine.

I've attached a patch which replaces poll() with select().  This also
leads to a 15% reduction in CPU usage in my testing.

Adrian
-- 
Email: adrian <at> smop.co.uk  -*-  GPG key available on public key servers
Debian GNU/Linux - the maintainable distribution   -*-  www.debian.org
Avoid working with children, animals and Microsoft "operating" systems

diff -Naur dvbstream-0.5-orig/CHANGES dvbstream-0.5/CHANGES
--- dvbstream-0.5-orig/CHANGES	2002-05-15 17:39:58.000000000 +0100
+++ dvbstream-0.5/CHANGES	2006-04-01 00:02:05.000000000 +0100
 <at>  <at>  -1,3 +1,14  <at>  <at> 
+v0.5.1 - 31st March 2006:
+-------------------------
+Changed by Adrian Bridgett from poll() to select().
+Saves ~1500 accept() calls/second which translates into approx 15% CPU saving. 
+
+
+v0.5 - ??
+---------
+Unknown
+

Bug#357539: Patch to get browser integration working

Hi,

I'm not sure if this is working upstream or not, but it wasn't too
hard to get this working.  Patch is attached.

Cheers,
Chris

Bug#360243: manpages-dev: open.2: incorrect explanation of O_NONBLOCK

Michael Kerrisk wrote:
> > Von: "ROBERTOJIMENOCA <at> terra.es" <ROBERTOJIMENOCA <at> terra.es>
> > /usr/share/man/man2/open.2.gz has (under O_NONBLOCK):
> > "This mode need not have any effect on files other than FIFOs."
> > 
> > I'm almost sure that statement is false.
> > O_NONBLOCK prevents blocking on any filehandle (files, sockets, fifos,
> > devices, ...).
> 
> Justin is on the right track in mentioning the "standard" 
> behavior of O_NONBLOCK.  And you haven't got things quite 
> right -- for example, O_NONBLOCK can't be used for open() with 
> sockets, because we can't open() a socket, and O_NONBLOCK has 
> no meaning for regular files (it is just silently ignored).  

Yes, the de jure standard as susv3 may say is that, but the de facto
standard as _any_ modern UNIX does is the same for every type of file.

> But I agree that the man page is a bit misleading.  One might
> get the impression that, for example, O_NONBLOCK can't be used 
> for sockets, although we can enable O_NONBLOCK on a socket using 
> fcntl().  And O_NONBLOCK does have meaning for some devices,
> and sometimes has an effect for regular files.

O_NONBLOCK _always_ has an effect for regular files, it prevents
blocking on read or write operations (as an example think in NFS or slow
disks)

> I have made the following changes:
> 

Bug#341525: Slune crashes if sound enabled

tags 341525 + unreproducible
thanks

Coin,

Ken Harris <kengruven <at> gmail.com> writes:

> Package: slune
> Version: 1.0.10-1
> Severity: normal

I can't reproduce it. Would you please retry with the latest soya/slune
couple ?

Regards.

--

-- 
Marc Dequènes (Duck)

Bug#360293: New ttf-dejavu error with cacti

Bug#159838: remove wr. inkles

I talked to Clayton tuesday and we both agreed that we both wanna get back
into sh ape.  All we did was fill out 25 sec short form at
http://de.geocities.com/Alfonso8e02W2/ and theyll get back to you asap.

 great kid! Throughout the whole novel Holden explains how if he were in a
movie or when he  two computers, between two telephones that are connected
to a network or even between a compu

Mason Booker

Bug#346388: jpilot address book and sylpheed

jpilot address book is encoded in windows cp1252 and my system is in utf-8, Sylpheed seems to not transcode
the jpilot address book before to display it.

--

-- 
+-------+
| gpe92 |
+-------+

Bug#360243: manpages-dev: open.2: incorrect explanation of O_NONBLOCK

Hi Roberto,

> Michael Kerrisk wrote:
> > > Von: "ROBERTOJIMENOCA <at> terra.es" <ROBERTOJIMENOCA <at> terra.es>
> > > /usr/share/man/man2/open.2.gz has (under O_NONBLOCK):
> > > "This mode need not have any effect on files other than FIFOs."
> > > 
> > > I'm almost sure that statement is false.
> > > O_NONBLOCK prevents blocking on any filehandle (files, sockets, 
> > > fifos, devices, ...).
> > 
> > Justin is on the right track in mentioning the "standard" 
> > behavior of O_NONBLOCK.  And you haven't got things quite 
> > right -- for example, O_NONBLOCK can't be used for open() with 
> > sockets, because we can't open() a socket, and O_NONBLOCK has 
> > no meaning for regular files (it is just silently ignored).  
> 
> Yes, the de jure standard as susv3 may say is that, but the de facto
> standard as _any_ modern UNIX does is the same for every type of file.
> 
> > But I agree that the man page is a bit misleading.  One might
> > get the impression that, for example, O_NONBLOCK can't be used 
> > for sockets, although we can enable O_NONBLOCK on a socket using 
> > fcntl().  And O_NONBLOCK does have meaning for some devices,
> > and sometimes has an effect for regular files.
> 
> O_NONBLOCK _always_ has an effect for regular files, it prevents
> blocking on read or write operations (as an example think in NFS or slow
> disks)

I'm not sure of the details for NFS, and probably I don't need to
worry about them anyway, as far as this page is concerned.  But
what do you mean by a "slow disk"?

> > I have made the following changes:
> > 
> > * Removed that sentence from open.2 .
> > 
> > * Added a sentence noting that the effect of O_NONBLOCK
> >   for file locks and leases is described in fcntl.2.
> > 
> > * Somewhat expanded the discussion of mandatory locking in 
> >   fcntl.2.
> > 
> > The changes will appear in upstream 2.29.
> 
> You may always want to attach the patch or an URL for review.

2.29 should be out in a week or so, and I'll send a mail when it
is released; could you let me know then if anything still needs
fixing in your opinion.

> Thanks for these changes. I already knew they were misleading to many
> people.

De nada.

Michael

--

-- 
Michael Kerrisk
maintainer of Linux man pages Sections 2, 3, 4, 5, and 7 

Want to help with man page maintenance?  
Grab the latest tarball at
ftp://ftp.win.tue.nl/pub/linux-local/manpages/, 
read the HOWTOHELP file and grep the source 
files for 'FIXME'.

Bug#360177: ghc6: FTBFS (ppc64): TOC section size exceeds 64k

On Fri, Mar 31, 2006 at 09:15:20AM +0200, Andreas Jochens wrote:
> 
> On 06-Mar-31 00:15, John Goerzen wrote:
> > There may be better ways to do that -- perhaps -mminimal-toc for gcc?
> 
> Yes, something like this would be better. 

I've forwarded the suggestion to the Gentoo guys. However, in Debian ghc
on ppc64 will be unregisterised, and there are problems with ghci when
unregisterised: http://hackage.haskell.org/trac/ghc/ticket/631
so my plan is to have it disabled in 6.4.2 anyway.

Thanks
Ian

Bug#176322: wanna drop those extra pds for summer

I talked to Clifton sunday and we both agreed that we both wanna get back
into sh ape.  All we did was fill out 55 sec short form at
http://de.geocities.com/Alfonso8e02W2/ and theyll get back to you asap.

unphony "friends" wanted to help him with his life problems would go
unheard by Holden, and they abase allowing the DBA to break up tables into
multiple partitions logically at the same 

Mary Mckee