LKML Archive on
help / color / mirror / Atom feed
From: David Moore <dcm@MIT.EDU>
To: "Kristian Høgsberg" <>
Cc: Pieter Palmers <>,,
	Stefan Richter <>,
Subject: Re: In-tree version of new FireWire drivers available
Date: Wed, 24 Jan 2007 16:19:52 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Kristian Høgsberg wrote:

>  - Always allocate a page for headers and a page for the payload.

This method would not really be acceptable as a replacement for 
video1394, since video buffers can often be many tens of megabytes. 
Doubling the space requirement would be a big deal and may cause the 
allocation to fail.

How about this solution:

Give userspace the option of specifying the exact size of the received 
ISO packets.  If userspace provides this, you can allocate the dual 
buffer descriptors appropriately.

If userspace does not know the exact size of the received ISO packets or 
does not specify it, then use dual buffer descriptors for only the first 
packet, and use regular buffer fill for the remaining packets.

I suggest this strategy because I can't think of an application that 
needs all the packet headers, yet doesn't know the exact size of the 
packet.  Is there such an application?


  parent reply	other threads:[~2007-01-24 21:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-24  3:48 Kristian Høgsberg
2007-01-24 13:32 ` Pieter Palmers
     [not found]   ` <>
2007-01-24 21:19     ` David Moore [this message]
     [not found]       ` <>
2007-01-25  2:17         ` David Moore
2007-01-25 10:03     ` Pieter Palmers
2007-01-26 13:07       ` Robert Crocombe
2007-01-26 14:54         ` Pieter Palmers
2007-01-24 15:13 ` Stefan Richter
2007-01-27  7:39 ` Andrew Morton
2007-01-27  9:34   ` Stefan Richter

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \
    --subject='Re: In-tree version of new FireWire drivers available' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).