From: "David S. Miller" <davem@davemloft.net>
To: leonid.grossman@neterion.com
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] Super TSO
Date: Thu, 19 May 2005 18:28:21 -0700 (PDT) [thread overview]
Message-ID: <20050519.182821.71087031.davem@davemloft.net> (raw)
In-Reply-To: <200505200125.j4K1PaVG015780@guinness.s2io.com>
From: "Leonid Grossman" <leonid.grossman@neterion.com>
Date: Thu, 19 May 2005 18:25:35 -0700
> Yes, I think I'm actually with you. As long as each page is physically
> continuous and therefore requires one descriptor per page, the total
> number of descriptors per packet will be only 64K / PAGE_SIZE (plus
> some for headers), and this is fully manageable from a NIC
> prospective.
Yes, that is exactly what happens.
next prev parent reply other threads:[~2005-05-20 1:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 2:24 [PATCH] Super TSO David S. Miller
2005-05-18 13:43 ` Andi Kleen
2005-05-18 19:57 ` David S. Miller
2005-05-20 0:15 ` Leonid Grossman
2005-05-20 0:21 ` David S. Miller
2005-05-20 0:36 ` Leonid Grossman
2005-05-20 0:55 ` David S. Miller
2005-05-20 1:25 ` Leonid Grossman
2005-05-20 1:28 ` David S. Miller [this message]
2005-05-20 0:45 ` Rick Jones
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=20050519.182821.71087031.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=leonid.grossman@neterion.com \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).