From: Andi Kleen <ak@suse.de>
To: Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Defragmentation proposal: preventative maintenance and cleanup [LONG]
Date: 07 Sep 2001 11:34:41 +0200 [thread overview]
Message-ID: <oupwv3buyxa.fsf@pigdrop.muc.suse.de> (raw)
In-Reply-To: <20010907062851Z16136-26184+30@humbolt.nl.linux.org.suse.lists.linux.kernel> <1426827386.999856726@[169.254.198.40].suse.lists.linux.kernel>
In-Reply-To: Alex Bligh - linux-kernel's message of "7 Sep 2001 11:13:45 +0200"
Alex Bligh - linux-kernel <linux-kernel@alex.org.uk> writes:
> I'd be especially interested to know how we'd solve this for the
> network stuff, which currently relies on physically contiguous packets
> in memory. This is a *HUGE* change I think (larger than any we'd
> make to the VM system).
It's already fixed in the network stack for at least the most important
protocols. The 2.4 stack supports iovecs of pages in skbs and also linked
lists of skbs for a single packet. The biggest killer used to be
defragmentation; that will just pass around a linked list now. There are
cases where defragmentation-into-a-big-buffer is still needed (e.g. for
most of netfilter), but fixing that is just small incremental change.
-Andi
next parent reply other threads:[~2001-09-07 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010907062851Z16136-26184+30@humbolt.nl.linux.org.suse.lists.linux.kernel>
[not found] ` <1426827386.999856726@[169.254.198.40].suse.lists.linux.kernel>
2001-09-07 9:34 ` Andi Kleen [this message]
2001-09-06 17:51 page_launder() on 2.4.9/10 issue Daniel Phillips
2001-09-06 21:01 ` [RFC] Defragmentation proposal: preventative maintenance and cleanup [LONG] Alex Bligh - linux-kernel
2001-09-07 6:35 ` Daniel Phillips
2001-09-07 8:58 ` Alex Bligh - linux-kernel
2001-09-07 9:15 ` Alex Bligh - linux-kernel
2001-09-07 9:28 ` Alex Bligh - linux-kernel
2001-09-07 21:38 ` Daniel Phillips
2001-09-07 21:56 ` Daniel Phillips
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=oupwv3buyxa.fsf@pigdrop.muc.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@alex.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®