MIME-Version: 1.0
References: <CAJNi4rNSHf3N6KrBNcVXKo-wjSPmZa2xan9WPmrER8Ttir-MDA@mail.gmail.com>
 <c708bced26624078842ff7d83e8597d7@AcuMS.aculab.com>
In-Reply-To: <c708bced26624078842ff7d83e8597d7@AcuMS.aculab.com>
From:   richard clark <richard.xnu.clark@gmail.com>
Date:   Thu, 16 Mar 2023 08:56:41 +0800
Message-ID: <CAJNi4rMB46z2hejoPCHyy+qDwE5U2D7H1OUwZ3+_pFAT9-cN3A@mail.gmail.com>
Subject: Re: Question about select and poll system call
To:     David Laight <David.Laight@aculab.com>
Cc:     "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Wed, Mar 15, 2023 at 4:59=E2=80=AFPM David Laight <David.Laight@aculab.c=
om> wrote:
>
> > 2. Can we unify the two different system calls? For example, using
> > poll(...) to implement the frontend select call(...), is there
> > something I'm missing for current implementation? The Cons and Pros,
> > etc
>
> The underlying code that implements them is common.
>
> Beware that the glibc select() wrappers have their own limit
> on the highest fd.
> Exceeding that limit (probably 1024) will cause buffer overruns
> in the application (One of the Android apps I uses crashes that way).

Ah, interesting. Seems glibc doesn't make that limit from my testing
code snippet in last email...

>
> select() also doesn't scale well for sparse lists of fds.
> So it really is best to use poll() and never select().
> (Although for very large fd lists epoll() may be a better choice.)
>
>         David
>
> -
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1=
 1PT, UK
> Registration No: 1397386 (Wales)