mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kuznet@ms2.inr.ac.ru
To: stodden@in.tum.DE (Daniel Stodden)
Cc: linux-kernel@vger.kernel.org
Subject: Re: NETIF_F_(SG|FRAGLIST|HIGHDMA) docs anywhere?
Date: Sat, 29 Dec 2001 22:16:21 +0300 (MSK)	[thread overview]
Message-ID: <200112291916.WAA12108@ms2.inr.ac.ru> (raw)
In-Reply-To: <1009610172.2105.0.camel@bitch> from "Daniel Stodden" at Dec 29, 1 10:45:00 am

Hello!

> 			so i guess supporting at least scatter/gather
> should give some performance improvements in order to get rid of
> skb_linearize() on xmit?

I beg pardon but before strating to fight problems, it is necessary
to force kernel to prepare something different of linear skbs. :-)

What's about checksumming? Do you plan to ignore it?


>			 since transmission is done completely by the
> local cpu, all of F_SG/FRAGLIST/HIGHDMA look relatively easy to
> implemement to me.=20

I see no connection between "cpu locality" and frgamtn hadling at all.


> frag_list seems to be the list involved with keeping track of ip
> fragmentation. so dev->hard_start_xmit() with frag_list set would only
> happen on routers or when??

In stock kernels: _never_. Packets are not defragmented by routers,
and netfilter linearizes everything in any case.

Anyway, if the driver is able to provide some facility, why not to do this?

> when is nr_frags>0? i've found some postings indicating sendfile(2) will
> benefit here. is this the only case?

Yes.

Which means that the task is not so sexy. :-)

Alexey

  reply	other threads:[~2001-12-29 19:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-29  7:16 Daniel Stodden
2001-12-29 19:16 ` kuznet [this message]
2001-12-29 11:14 Manfred Spraul

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=200112291916.WAA12108@ms2.inr.ac.ru \
    --to=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stodden@in.tum.DE \
    /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®