From: Vlastimil Babka <vbabka@suse.cz>
To: David Laight <David.Laight@ACULAB.COM>,
Nicholas Piggin <npiggin@gmail.com>
Cc: Jason Baron <jbaron@akamai.com>,
Hillf Danton <hillf.zj@alibaba-inc.com>,
'Alexander Viro' <viro@zeniv.linux.org.uk>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
'Michal Hocko' <mhocko@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH] fs/select: add vmalloc fallback for select(2)
Date: Wed, 28 Sep 2016 22:04:50 +0200 [thread overview]
Message-ID: <32941b8b-ec1a-fc5c-90aa-e2372680f1b3@suse.cz> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6DB010AAC6@AcuExch.aculab.com>
On 09/28/2016 06:30 PM, David Laight wrote:
> From: Vlastimil Babka
>> Sent: 27 September 2016 12:51
> ...
>> Process name suggests it's part of db2 database. It seems it has to implement
>> its own interface to select() syscall, because glibc itself seems to have a
>> FD_SETSIZE limit of 1024, which is probably why this wasn't an issue for all the
>> years...
>
> ISTR the canonical way to increase the size being to set FD_SETSIZE
> to a larger value before including any of the headers.
>
> Or doesn't that work with linux and glibc ??
Doesn't seem so.
>
> David
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-09-28 20:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 15:28 Vlastimil Babka
2016-09-22 16:24 ` Eric Dumazet
2016-09-22 16:40 ` Vlastimil Babka
2016-09-23 6:42 ` Hillf Danton
2016-09-23 7:24 ` Nicholas Piggin
2016-09-23 16:47 ` Jason Baron
2016-09-27 8:44 ` Vlastimil Babka
2016-09-27 11:24 ` Nicholas Piggin
2016-09-27 11:37 ` David Laight
2016-09-27 11:42 ` Nicholas Piggin
2016-09-27 11:51 ` Vlastimil Babka
2016-09-28 16:30 ` David Laight
2016-09-28 20:04 ` Vlastimil Babka [this message]
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=32941b8b-ec1a-fc5c-90aa-e2372680f1b3@suse.cz \
--to=vbabka@suse.cz \
--cc=David.Laight@ACULAB.COM \
--cc=eric.dumazet@gmail.com \
--cc=hillf.zj@alibaba-inc.com \
--cc=jbaron@akamai.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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