From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: knicholson@corp.iready.com (Ken Nicholson)
Cc: alan@lxorguk.ukuu.org.uk ('Alan Cox'),
Venkateshr@ami.com, pollard@tomcat.admin.navo.hpc.mil,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] Direct Sockets Support??
Date: Tue, 8 May 2001 14:04:45 +0100 (BST) [thread overview]
Message-ID: <E14x7AW-0005bf-00@the-village.bc.nu> (raw)
In-Reply-To: <034670D62D19D31180990090277A37B701811D72@mercury.corp.iready.com> from "Ken Nicholson" at May 07, 2001 06:55:08 PM
> A couple of concerns I have:
> * How to pin or pagelock the application buffer without
> making a kernel transition.
You need to pin them in advance. And pinning pages is _expensive_ so you dont
want to keep pinning/unpinning pages
> * Assuming the memory can be locked down, how can a list
> of physical memory ranges be obtained (necessary to support
> scatter/gather DMA? Is kiobufs suitable with it's page-alignment
> constraints? If kiobufs will work, how can the kernel transition be
> avoided?
kiovecs will do that. It might be a little heavyweight but that should improve
in 2.5 as we move to a slightly lighter model
> WinSock Direct seems to address these concerns. These issues
> become important at 1Gb and 10Gb speeds.
1Gbit - not really, 10Gbit yes
next parent reply other threads:[~2001-05-08 13:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <034670D62D19D31180990090277A37B701811D72@mercury.corp.iready.com>
2001-05-08 13:04 ` Alan Cox [this message]
2001-05-08 20:00 ` Pete Wyckoff
2001-05-08 20:18 Venkatesh Ramamurthy
2001-05-08 20:50 ` Alan Cox
2001-05-08 21:32 ` 'Pete Wyckoff'
-- strict thread matches above, loose matches on Subject: below --
2001-05-03 20:55 Venkatesh Ramamurthy
2001-05-03 20:40 Venkatesh Ramamurthy
2001-05-03 21:52 ` Alan Cox
2001-05-03 20:23 Jesse Pollard
2001-05-03 19:25 Venkatesh Ramamurthy
2001-05-03 20:29 ` Alan Cox
2001-05-03 19:23 Jesse Pollard
2001-05-03 18:59 Venkatesh Ramamurthy
2001-05-03 20:17 ` Alan Cox
[not found] <007901c0d3fd$ea3f0880$7253e59b@megatrends.com>
2001-05-03 18:34 ` Alan Cox
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=E14x7AW-0005bf-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Venkateshr@ami.com \
--cc=knicholson@corp.iready.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pollard@tomcat.admin.navo.hpc.mil \
/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®