From: "David S. Miller" <davem@davemloft.net>
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: nickpiggin@yahoo.com.au
Cc: herbert@gondor.apana.org.au, mbligh@mbligh.org,
jschopp@austin.ibm.com, mel@csn.ul.ie, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: Avoiding external fragmentation with a placement policy Version 12
Date: Sun, 05 Jun 2005 12:52:49 -0700 (PDT) [thread overview]
Date: Sat, 04 Jun 2005 12:15:46 +1000 [thread overview]
Message-ID: <20050605.125249.104050648.davem@davemloft.net> (raw)
In-Reply-To: <42A10ED2.7020205@yahoo.com.au>
> Herbert Xu wrote:
> > With Dave's latest super-TSO patch, TCP over loopback will only be
> > doing order-0 allocations in the common case. UDP and others may
> > still do large allocations but that logic is all localised in
> > ip_append_data.
> >
> > So if we wanted we could easily remove most large allocations over
> > the loopback device.
>
> I would be very interested to look into that. I would be
> willing to do benchmarks on a range of machines too if
> that would be of any use to you.
Even without the super-TSO patch, we never do larger than
PAGE_SIZE allocations for sendmsg() when the device is
scatter-gather capable (as indicated in netdev->flags).
Loopback does set this bit.
This PAGE_SIZE limit comes from net/ipv4/tcp.c:select_size().
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-06-05 19:52 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 11:20 Mel Gorman
2005-06-01 20:55 ` Joel Schopp
2005-06-01 23:09 ` Nick Piggin
2005-06-01 23:23 ` David S. Miller, Nick Piggin
2005-06-01 23:28 ` Martin J. Bligh
2005-06-01 23:43 ` Nick Piggin
2005-06-02 0:02 ` Martin J. Bligh
2005-06-02 0:20 ` Nick Piggin
2005-06-02 13:55 ` Mel Gorman
2005-06-02 15:52 ` Joel Schopp
2005-06-02 19:50 ` Ray Bryant
2005-06-02 20:10 ` Joel Schopp
2005-06-04 16:09 ` Marcelo Tosatti
2005-06-03 3:48 ` Nick Piggin
2005-06-03 4:49 ` David S. Miller, Nick Piggin
2005-06-03 5:34 ` Martin J. Bligh
2005-06-03 5:37 ` David S. Miller, Martin J. Bligh
2005-06-03 5:42 ` Martin J. Bligh
2005-06-03 5:51 ` David S. Miller, Martin J. Bligh
2005-06-03 13:13 ` Mel Gorman
2005-06-03 6:43 ` Nick Piggin
2005-06-03 13:57 ` Martin J. Bligh
2005-06-03 16:43 ` Dave Hansen
2005-06-03 18:43 ` David S. Miller, Dave Hansen
2005-06-04 1:44 ` Herbert Xu
2005-06-04 2:15 ` Nick Piggin
2005-06-05 19:52 ` David S. Miller, Nick Piggin [this message]
2005-06-03 13:05 ` Mel Gorman
2005-06-03 14:00 ` Martin J. Bligh
2005-06-08 17:03 ` Mel Gorman
2005-06-08 17:18 ` Martin J. Bligh
2005-06-10 16:20 ` Christoph Lameter
2005-06-10 17:53 ` Steve Lord
2005-06-02 18:28 ` Andi Kleen
2005-06-02 18:42 ` Martin J. Bligh
2005-06-02 13:15 ` Mel Gorman
2005-06-02 14:01 ` Martin J. Bligh
[not found] ` <20050603174706.GA25663@localhost.localdomain>
2005-06-03 17:56 ` Martin J. Bligh
2005-06-01 23:47 ` Mike Kravetz
2005-06-01 23:56 ` Nick Piggin
2005-06-02 0:07 ` Mike Kravetz
2005-06-02 9:49 ` 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=20050605.125249.104050648.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=herbert@gondor.apana.org.au \
--cc=jschopp@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@mbligh.org \
--cc=mel@csn.ul.ie \
--cc=nickpiggin@yahoo.com.au \
/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