public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: gibbs@scsiguy.com
Cc: kevin.vanmaren@unisys.com, linux-kernel@vger.kernel.org
Subject: Re: With Daniel Phillips Patch
Date: Wed, 22 Aug 2001 18:45:12 -0700 (PDT)	[thread overview]
Message-ID: <20010822.184512.77060492.davem@redhat.com> (raw)
In-Reply-To: <200108230140.f7N1etY22587@aslan.scsiguy.com>
In-Reply-To: <20010822.183109.34763266.davem@redhat.com> <200108230140.f7N1etY22587@aslan.scsiguy.com>

   From: "Justin T. Gibbs" <gibbs@scsiguy.com>
   Date: Wed, 22 Aug 2001 19:40:55 -0600

   You have to keep track of the significant bits in the dma_addr_t
   regardless of its size, so you put it into your TX descriptor's (or
   what have you) native format that doesn't waste any space.  You don't
   need to keep the full dma_addr_t around.  Perhaps this is just sloppy
   programming?
   
Some devices keep these in registers and advance them as the
dma progresses.  The only reliable way is by keeping track
of it in software.

   If you don't want to take part in technical discussions, you should
   work in closed source. 8-)

It's not open source, it's "dumb source" I have problems with.
A lot of discussions here end up being of that variety.

Later,
David S. Miller
davem@redhat.com
   

  reply	other threads:[~2001-08-23  1:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-23  1:06 With Daniel Phillips Patch Van Maren, Kevin
2001-08-23  1:31 ` David S. Miller
2001-08-23  1:40   ` Justin T. Gibbs
2001-08-23  1:45     ` David S. Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-23  2:22 Van Maren, Kevin
2001-08-23  2:26 ` David S. Miller
2001-08-22  6:46 With Daniel Phillips Patch (was: aic7xxx with 2.4.9 on 7899P) Jens Axboe
2001-08-22 13:24 ` Justin T. Gibbs
2001-08-22 15:05   ` With Daniel Phillips Patch David S. Miller
2001-08-22 18:21     ` Gérard Roudier
2001-08-22 18:32       ` David S. Miller
2001-08-22 18:32     ` Justin T. Gibbs
2001-08-22 18:46       ` David S. Miller
2001-08-22 19:41         ` Justin T. Gibbs
2001-08-22 20:19           ` David S. Miller
2001-08-22 21:07         ` Gérard Roudier
2001-08-22 21:14           ` David S. Miller
2001-08-22 21:14           ` David S. Miller
2001-08-22 21:40           ` Justin T. Gibbs
2001-08-22 23:09             ` David S. Miller
2001-08-23  0:01               ` Justin T. Gibbs
2001-08-23  0:40                 ` David S. Miller
2001-08-23  0:55                   ` Justin T. Gibbs
2001-08-23  1:03                     ` Matthew Jacob
2001-08-23  1:08                     ` David S. Miller
2001-08-23  1:32                       ` Justin T. Gibbs
2001-08-23  1:39                         ` David S. Miller
2001-08-23  1:49                           ` Justin T. Gibbs

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=20010822.184512.77060492.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=gibbs@scsiguy.com \
    --cc=kevin.vanmaren@unisys.com \
    --cc=linux-kernel@vger.kernel.org \
    /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