From: Davide Libenzi <davidel@xmailserver.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Hanna Linder <hannal@us.ibm.com>,
Benjamin LaHaise <bcrl@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<linux-aio@kvack.org>
Subject: Re: [PATCH] sys_epoll system call interface to /dev/epoll
Date: Fri, 18 Oct 2002 15:45:51 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0210181538100.1537-100000@blue1.dev.mcafeelabs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0210181504470.11349-100000@penguin.transmeta.com>
On Fri, 18 Oct 2002, Linus Torvalds wrote:
>
> On Fri, 18 Oct 2002, Hanna Linder wrote:
> >
> > You said earlier that you didn't like epoll being
> > in /dev. How about a system call interface instead? this
> > patch provides the skeleton for that system call. We
> > can have Davide's patch ported into it ASAP if you include
> > this by the freeze.
>
> I like it noticeably better as a system call, so it's maybe worth
> discussing. It's not going to happen before I leave (very early tomorrow
> morning), but if people involved agree on this and clean patches to
> actiually add the code (not just system call stubs) can be made..
Linus, yesterday I was sugesting Hanna to use most of the existing code
and to make :
int sys_epoll_create(int maxfds);
to actually return an fd. Basically during this function call the code
allocates a file*, initialize it, allocates a free fd, maps the file* to
the fd, creates the vma* for the shared events area between the kernel and
user space, maps allocated kernel pages to the vma*, install the vma* and
returns the fd. In this way we can avoid the sys_epoll_close() and close()
can be used. Also the task cleanup comes for free being linked to a file*.
In this way also users that are using /dev/epoll in the old way can
continue to use it, being the skeleton code the same.
Do I have to guess that you do not like this idea ?
- Davide
next prev parent reply other threads:[~2002-10-18 22:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 22:00 Hanna Linder
2002-10-18 22:05 ` Linus Torvalds
2002-10-18 22:45 ` Davide Libenzi [this message]
2002-10-18 22:51 ` Linus Torvalds
2002-10-18 23:09 ` Shailabh Nagar
2002-10-18 23:27 ` Linus Torvalds
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=Pine.LNX.4.44.0210181538100.1537-100000@blue1.dev.mcafeelabs.com \
--to=davidel@xmailserver.org \
--cc=bcrl@redhat.com \
--cc=hannal@us.ibm.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®