All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@transmeta.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Kenn Humborg <kenn@linux.ie>, "H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org
Subject: Re: kmalloc() alignment
Date: Mon, 05 Mar 2001 21:05:04 -0800	[thread overview]
Message-ID: <3AA47000.5CE66D95@transmeta.com> (raw)
In-Reply-To: <E14a6zQ-0008Gz-00@the-village.bc.nu>

Alan Cox wrote:
> 
> > > It might be worth asking the question if larger blocks are more
> > > aligned?
> >
> > OK, I'll bite...
> > Are larger blocks more aligned?
> 
> Only get_free_page()
> 

I wonder if it would be practical/reasonable to guarantee better
alignment for larger allocations (at least for sizes that are powers of
two); especially 8- and 16-byte alignment is sometimes necessary.

	-hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt

  reply	other threads:[~2001-03-06  5:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-04 22:41 kmalloc() alignment Manfred Spraul
2001-03-06  0:06 ` Kenn Humborg
2001-03-06  0:15   ` H. Peter Anvin
2001-03-06  0:29     ` Kenn Humborg
2001-03-06  2:14       ` Alan Cox
2001-03-06  5:05         ` H. Peter Anvin [this message]
2001-03-06  8:31     ` Rogier Wolff
2001-03-06 12:10       ` Xavier Bestel
2001-03-07  7:53       ` RAID, 2.4.2 and Buslogic Jauder Ho
2001-03-07  8:20         ` Andreas Dilger
  -- strict thread matches above, loose matches on Subject: below --
2004-10-19 14:51 kmalloc alignment Atsushi Nemoto
2004-10-19 16:59 ` Ralf Baechle
2004-10-20  5:56   ` Atsushi Nemoto
2003-05-05 22:03 Thomas Heinz
2001-03-04 22:17 kmalloc() alignment Kenn Humborg
2001-03-04 22:34 ` Alan Cox
2001-03-05  9:40   ` Rogier Wolff
2001-03-05 13:24     ` Alan Cox
2001-03-05 13:22       ` Rogier Wolff
2001-03-06  8:59   ` Philipp Rumpf
2001-03-06 12:14     ` Alan Cox

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=3AA47000.5CE66D95@transmeta.com \
    --to=hpa@transmeta.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hpa@zytor.com \
    --cc=kenn@linux.ie \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.