linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mel@csn.ul.ie>
To: Zhu Yi <yi.zhu@intel.com>
Cc: "Chatre, Reinette" <reinette.chatre@intel.com>,
	Frans Pop <elendil@planet.nl>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	"John W. Linville" <linville@tuxdriver.com>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ipw3945-devel@lists.sourceforge.net"
	<ipw3945-devel@lists.sourceforge.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	"cl@linux-foundation.org" <cl@linux-foundation.org>,
	"Krauss, Assaf" <assaf.krauss@intel.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	"Abbas, Mohamed" <mohamed.abbas@intel.com>
Subject: Re: iwlagn: order 2 page allocation failures
Date: Mon, 14 Sep 2009 14:06:12 +0100	[thread overview]
Message-ID: <20090914130612.GA11778@csn.ul.ie> (raw)
In-Reply-To: <1252897270.5650.169.camel@debian>

On Mon, Sep 14, 2009 at 11:01:10AM +0800, Zhu Yi wrote:
> On Fri, 2009-09-11 at 16:47 +0800, Mel Gorman wrote:
> > On Thu, Sep 10, 2009 at 02:14:50PM -0700, reinette chatre wrote:
> > > On Thu, 2009-09-10 at 02:02 -0700, Mel Gorman wrote:
> > > 
> > > > 
> > > > As a total aside, there is still the problem that the driver is depending on
> > > > order-2 allocations. On systems without swap, the allocation problem could be
> > > > more severe as there are fewer pages the system can use to regain contiguity.
> > > 
> > > I looked more at the implementation and hardware interface but I do not
> > > see a way around this. We have to provide 8k buffer to device, and we
> > > have to make sure it is aligned. 
> > > 
> > 
> > That would imply an order-1 allocation instead of an order-2 though so
> > it would appear than we are being worse than we have to. It would appear
> > to be because of this +256 bytes that goes onto every buffer.
> > 
> > > Do you have any suggestions?
> > > 
> > 
> > Nothing concrete. Finding an alternative to having the socket buffer
> > 8192+256 to make it an order-1 allocation would be an improvement but I
> > don't know how that should be tackled. Lacking the hardware, I can't
> > experiment myself :(
> 
> Essentially, the hardware only requires an order-1 allocation aligned on
> 256 bytes boundary. But as it is used as an SKB, a trailing struct
> skb_shared_info is added. This forces us to both increase the order and
> do alignment ourselves. I believe some improvement could be done here.
> But it should not be an easy one.
> 

Probably not. I can only assume that moving the location of
skb_shared_info such that it is sometimes located after the buffer and
sometimes allocated via a separate kmalloc() would be a significant
undertaking.

> BTW, does SLAB/SLUB guarantee size of multiple PAGE_SIZE __kmalloc()
> allocation align on PAGE_SIZE (or 256 bytes) boundary?
> 

Page-aligned.

-- 
Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab

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

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-06  7:40 iwlagn: order 2 page allocation failures Frans Pop
2009-09-06  8:14 ` Pekka Enberg
2009-09-06  8:28   ` Frans Pop
2009-09-06  8:35     ` Pekka Enberg
2009-09-08 10:54       ` Mel Gorman
2009-09-08 11:11         ` Pekka Enberg
2009-09-08 14:17           ` John W. Linville
2009-09-08 14:59             ` Larry Finger
2009-09-09 15:04               ` Mel Gorman
2009-09-09 15:59                 ` Frans Pop
2009-09-09 16:55                   ` Mel Gorman
2009-09-09 17:19                     ` Frans Pop
2009-09-16 14:36                       ` Frans Pop
2009-09-16 15:02                         ` Mel Gorman
2009-09-16 15:37                           ` Frans Pop
2009-09-16 16:26                           ` reinette chatre
2009-09-09 20:05                     ` reinette chatre
2009-09-10  1:48                       ` Frans Pop
2009-09-10  9:02                       ` Mel Gorman
2009-09-10 18:15                         ` reinette chatre
2009-09-10 18:43                           ` Frans Pop
2009-09-10 18:50                             ` reinette chatre
2009-09-11  8:45                           ` Mel Gorman
2009-09-11 16:14                             ` reinette chatre
2009-09-10 21:14                         ` reinette chatre
2009-09-11  8:47                           ` Mel Gorman
2009-09-14  3:01                             ` Zhu Yi
2009-09-14 13:06                               ` Mel Gorman [this message]
2009-09-15  8:30                                 ` alloc skb based on a given data buffer Zhu Yi
2009-09-15  8:33                                   ` David Miller
2009-09-15  8:57                                     ` Zhu Yi
2009-09-15  9:09                                       ` David Miller
2009-09-15  9:15                                         ` Zhu Yi
2009-09-15 15:30                                           ` Johannes Berg
2009-09-15 21:16                                             ` David Miller
2009-09-19  5:56                                               ` Johannes Berg
2009-09-14 15:42                               ` iwlagn: order 2 page allocation failures Christoph Lameter
2009-09-14 17:59                                 ` Mel Gorman
2009-09-14 18:04                                   ` Christoph Lameter
2009-09-10  8:18                     ` Pekka Enberg
2009-09-10 12:34                       ` Mel Gorman
2009-09-10 12:39                         ` Pekka Enberg
2009-09-10 12:58                           ` Mel Gorman

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=20090914130612.GA11778@csn.ul.ie \
    --to=mel@csn.ul.ie \
    --cc=Larry.Finger@lwfinger.net \
    --cc=akpm@linux-foundation.org \
    --cc=assaf.krauss@intel.com \
    --cc=cl@linux-foundation.org \
    --cc=elendil@planet.nl \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mohamed.abbas@intel.com \
    --cc=penberg@cs.helsinki.fi \
    --cc=reinette.chatre@intel.com \
    --cc=yi.zhu@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;
as well as URLs for NNTP newsgroup(s).