From: David Miller <davem@davemloft.net>
To: dhananjay.phadke@qlogic.com
Cc: davem@davemloft.com, netdev@vger.kernel.org
Subject: Re: [PATCH NEXT 1/3] netxen: fix lro buffer allocation
Date: Thu, 03 Sep 2009 20:33:55 -0700 (PDT) [thread overview]
Message-ID: <20090903.203355.227030741.davem@davemloft.net> (raw)
In-Reply-To: <7608421F3572AB4292BB2532AE89D565865FA8A557@AVEXMB1.qlogic.org>
From: Dhananjay Phadke <dhananjay.phadke@qlogic.com>
Date: Thu, 3 Sep 2009 20:24:15 -0700
>> But if the page allocator can't satisfy allocation requests
>> it doesn't matter how many microseconds you're saving here.
>>
>> I think you're priorities are backwards.
>
> Ok whatever. Whether I request 9k or 12k, page allocator
> is digging 16k chunks.
>
> When there's enough memory, every cycle saved is important
> for firmware. I would love to enable fragmented rx, if it's
> not affecting throughput.
Ok.
Just FYI I won't be surprised if SLAB/SLUB/SLQB at some point
handle this situation differently.
prev parent reply other threads:[~2009-09-04 3:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 23:10 [PATCH NEXT 1/3] netxen: fix lro buffer allocation Dhananjay Phadke
2009-09-03 23:10 ` [PATCH NEXT 2/3] netxen: remove duplicate napi_add Dhananjay Phadke
2009-09-04 3:07 ` David Miller
2009-09-03 23:10 ` [PATCH NEXT 3/3] netxen: fix infinite loop on dma mapping failure Dhananjay Phadke
2009-09-04 3:07 ` David Miller
2009-09-04 3:06 ` [PATCH NEXT 1/3] netxen: fix lro buffer allocation David Miller
2009-09-04 3:14 ` Dhananjay Phadke
2009-09-04 3:15 ` David Miller
2009-09-04 3:24 ` Dhananjay Phadke
2009-09-04 3:33 ` David Miller [this message]
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=20090903.203355.227030741.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=davem@davemloft.com \
--cc=dhananjay.phadke@qlogic.com \
--cc=netdev@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 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).