From: Ingo Molnar <mingo@elte.hu>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
David Miller <davem@davemloft.net>
Subject: Re: [patch 3/7] epoll keyed wakeups - introduce key-aware wakeup macros
Date: Sat, 31 Jan 2009 04:30:35 +0100 [thread overview]
Message-ID: <20090131033035.GA26640@elte.hu> (raw)
In-Reply-To: <send-serie.davidel@xmailserver.org.16376.1233372317.3>
* Davide Libenzi <davidel@xmailserver.org> wrote:
> +#define wake_up(x) kwake_up(x, NULL)
> +#define wake_up_nr(x, nr) kwake_up_nr(x, nr, NULL)
> +#define wake_up_all(x) kwake_up_all(x, NULL)
> +#define wake_up_locked(x) kwake_up_locked(x, NULL)
> +
> +#define wake_up_interruptible(x) kwake_up_interruptible(x, NULL)
> +#define wake_up_interruptible_nr(x, nr) kwake_up_interruptible_nr(x, nr, NULL)
> +#define wake_up_interruptible_all(x) kwake_up_interruptible_all(x, NULL)
> +#define wake_up_interruptible_sync(x) kwake_up_interruptible_sync(x, NULL)
i like the patchset - nice work!
One minor worry i have: these wakeup calls are _very_ common in the
kernel, and this patch adds an extra parameter to it that is unused (NULL)
in 99% of the cases.
Would be nice to see the kernel image size increase due to this change
(which gives a good measure about how much of an issue this is).
If it's of any worrying level, it might make sense to keep the original
functions untouched, and introduce a second entry point that has one more
parameter. Ok?
Ingo
next prev parent reply other threads:[~2009-01-31 3:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 3:25 [patch 3/7] epoll keyed wakeups - introduce key-aware wakeup macros Davide Libenzi
2009-01-31 3:30 ` Ingo Molnar [this message]
2009-01-31 3:50 ` Davide Libenzi
2009-01-31 3:57 ` Linus Torvalds
2009-01-31 13:06 ` Ingo Molnar
2009-01-31 18:57 ` Davide Libenzi
2009-01-31 9:25 ` Alan Cox
2009-01-31 19:03 ` Davide Libenzi
2009-01-31 3:49 ` Linus Torvalds
2009-01-31 4:01 ` Davide Libenzi
2009-01-31 4:57 ` wli
2009-01-31 19:08 ` Davide Libenzi
2009-01-31 21:28 ` wli
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=20090131033035.GA26640@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@davemloft.net \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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