Linux-kernel mailing list archive 2000-29,: Re: [RFC] solution for the inet_ntoa problem, buffer allocator

# Re: [RFC] solution for the inet_ntoa problem, buffer allocator

Oliver Xymoron (oxymoron@waste.org)
Sun, 16 Jul 2000 20:52:03 -0500 (CDT)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Igmar Palsenberg: "Re: Closing the FILE object."
- Previous message: Igmar Palsenberg: "Re: Q: how to debug lockups?"

On Sat, 8 Jul 2000, Olaf Titz wrote:

> > > sometimes use sort of a round-robbin buffer, shared by several
> > > functions. This way, I can call the same function several times
> > > without allocating memory, and the number of calls is just limited
> > > by the total size. Here comes an example (from scratch, completely
> > > untested).
> > >
> > > Any comments ?
> >
> > Not threadsafe.
>
> This one is threadsafe (in the limit given by the number of buffers,
> you probably want to configure that depending on the number of CPUs).

But now it's a brand new lock contention point! That's not much of an
improvement. It took me all of 20 minutes to replace all the instances of
inet_ntoa with inet_ntoa2, why all the effort to make the inherently
troubled inet_ntoa work?

    --
     "Love the dolphins," she advised him. "Write by W.A.S.T.E.."

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/

- Next message: Igmar Palsenberg: "Re: Closing the FILE object."
- Previous message: Igmar Palsenberg: "Re: Q: how to debug lockups?"