From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: David Miller <davem@davemloft.net>
Cc: sri@us.ibm.com, netdev@vger.kernel.org
Subject: Re: [PATCH RESEND 2/2] update sunrpc to use in-kernel sockets API
Date: Tue, 08 Aug 2006 23:16:42 -0400 [thread overview]
Message-ID: <1155093402.5731.35.camel@localhost> (raw)
In-Reply-To: <20060808.170941.71164303.davem@davemloft.net>
On Tue, 2006-08-08 at 17:09 -0700, David Miller wrote:
> Trond, I think the highmem check in xs_sendpages() is completely
> bogus, do you mind if we remove it? :-)
>
> The socket layer will properly check the device to make sure it
> can handle highmem pages, and if not it will copy the data into
> a low-mem page as-needed.
If the special case is no longer useful, then I for one am quite happy
to get rid of it.
Cheers,
Trond
next prev parent reply other threads:[~2006-08-09 3:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 23:00 [PATCH RESEND 2/2] update sunrpc to use in-kernel sockets API Sridhar Samudrala
2006-08-08 3:59 ` David Miller
2006-08-08 17:19 ` Sridhar Samudrala
2006-08-09 0:09 ` David Miller
2006-08-09 3:16 ` Trond Myklebust [this message]
2006-08-09 17:34 ` Sridhar Samudrala
2006-08-10 0:03 ` David Miller
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=1155093402.5731.35.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sri@us.ibm.com \
/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