From: Keir Fraser <keir@xensource.com>
To: Jan Beulich <jbeulich@novell.com>, David Edmondson <dme@sun.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: 3.0.4 (and earlier): skbuff_ctor() use of xen_create_contiguous_region()
Date: Fri, 09 Mar 2007 14:08:45 +0000 [thread overview]
Message-ID: <C2171AED.B240%keir@xensource.com> (raw)
In-Reply-To: <45F164F7.76E4.0078.0@novell.com>
On 9/3/07 12:45, "Jan Beulich" <jbeulich@novell.com> wrote:
> I understand that, but what I wanted clarification on is whether this is
> only for performance, not for correctness (and performance would still
> suffer if the allocation turns out to be beyond the physical reach of the
> particular NIC).
Yes, and yes (specifically primarily the jumbo-frame receive case, as
described in my previous email). Thus you may want to consider keeping the
patch in your own kernel.
-- Keir
next prev parent reply other threads:[~2007-03-09 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 12:17 3.0.4 (and earlier): skbuff_ctor() use of xen_create_contiguous_region() Jan Beulich
2007-03-09 12:37 ` David Edmondson
2007-03-09 12:45 ` Jan Beulich
2007-03-09 12:58 ` David Edmondson
2007-03-09 14:08 ` Keir Fraser [this message]
2007-03-09 14:06 ` Keir Fraser
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=C2171AED.B240%keir@xensource.com \
--to=keir@xensource.com \
--cc=dme@sun.com \
--cc=jbeulich@novell.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.