From: Daniel Stodden <stodden@in.tum.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: NETIF_F_(SG|FRAGLIST|HIGHDMA) docs anywhere?
Date: 29 Dec 2001 08:16:12 +0100 [thread overview]
Message-ID: <1009610172.2105.0.camel@bitch> (raw)
[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]
hi.
software-only network device, currently implementing none of the
dev->features flags.
the driver transmits packets via pci dma to other processors residing on
a shared PCI bus segment. so i guess supporting at least scatter/gather
should give some performance improvements in order to get rid of
skb_linearize() on xmit? since transmission is done completely by the
local cpu, all of F_SG/FRAGLIST/HIGHDMA look relatively easy to
implemement to me.
my major problem is test cases and getting the picture behind these
structures. is there any documentation around on the
skb_shinfo(skb)->frags and skb_shinfo(skb)->frag_list stuff? i've spend
quite some time now trying to figure out exactly under which
circumstances which of both applies. not too successful i must admit :)
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??
when is nr_frags>0? i've found some postings indicating sendfile(2) will
benefit here. is this the only case? need some test code..
any hint appreciated,
dns
--
___________________________________________________________________________
mailto:stodden@in.tum.de
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2001-12-29 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-29 7:16 Daniel Stodden [this message]
2001-12-29 19:16 ` NETIF_F_(SG|FRAGLIST|HIGHDMA) docs anywhere? kuznet
-- strict thread matches above, loose matches on Subject: below --
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=1009610172.2105.0.camel@bitch \
--to=stodden@in.tum.de \
--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