public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Arjan van de Ven <arjan@infradead.org>,
	linux-kernel@vger.kernel.org, lenb@kernel.org, mingo@elte.hu,
	yanmin_zhang@linux.intel.com, torvalds@linux-foundation.org,
	jens.axboe@oracle.com, David Howells <dhowells@redhat.com>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Subject: Re: PATCH] cpuidle: A new variant of the menu governor to boost IO performance
Date: Mon, 14 Sep 2009 18:09:21 +0900	[thread overview]
Message-ID: <4AAE0841.6000305@kernel.org> (raw)
In-Reply-To: <1252916128.5699.41.camel@laptop>

Hello,

Peter Zijlstra wrote:
>> If someone has any better ideas, I would happy to remove the annoying
>> restriction.
> 
> That sounds like a variable __attribute__((no-explicit-relocs)) should
> be proposed to the GCC folks or something. Then we can at least have a
> hope of lifting this restriction some time in the future.
> 
> (Alternatively we build the full alpha kernel with
> --mno-explicit-relocs, but that would be sub-optimal as well)
> 
> Not sure if s390 has anything similar..

If possible, something like __attribute__((dont-expect-it-to-be-near))
would be very nice in this case.

> Alternatively we could file it as a bug, since the symbols are in a
> custom .section, which is a strong indication we're going to play funny
> games anyway.

This sounds quite appealing but I think it has certain possibility of
coming back and bite us in the rear.

Hmmm... Offsets for symbols which fit in the first chunk are
guaranteed to be addressable with the reduced range and thus the weak
trick is only necessary for modules, so a solution we can implement in
kernel proper is to reserve address range for module text and data to
be loaded near the builtin text and data.  Percpu already supports
reservation in the first chunk (for x86-64 for example) so that part
is already there.  Ah... only if s390 and alpha are a little easier to
come by.  :-(

Thanks.

-- 
tejun

  reply	other threads:[~2009-09-14  9:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11 15:40 PATCH] cpuidle: A new variant of the menu governor to boost IO performance Arjan van de Ven
2009-09-11 16:37 ` Jens Axboe
2009-09-11 19:16 ` John Stoffel
2009-09-11 19:51   ` Arjan van de Ven
2009-09-14  3:30   ` Zhang, Yanmin
2009-09-11 22:03 ` Matthew Garrett
2009-09-12  3:26   ` Arjan van de Ven
2009-09-12 11:39     ` Matthew Garrett
2009-09-12 14:04       ` Arjan van de Ven
2009-09-13 23:30 ` Andrew Morton
2009-09-14  2:45   ` Arjan van de Ven
2009-09-14  7:43 ` Andrew Morton
2009-09-14  8:04   ` Tejun Heo
2009-09-14  8:15     ` Peter Zijlstra
2009-09-14  9:09       ` Tejun Heo [this message]
2009-09-14 20:31   ` Arjan van de Ven

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=4AAE0841.6000305@kernel.org \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=dhowells@redhat.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=jens.axboe@oracle.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --cc=yanmin_zhang@linux.intel.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