mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Egger <de@axiros.com>
To: Ross Biro <ross.biro@gmail.com>
Cc: linux-kernel Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC/Patch 2.6.11] Take control of PCI Master Abort Mode
Date: Thu, 14 Apr 2005 21:14:26 +0200	[thread overview]
Message-ID: <d2274e05b0524222d01c2d584297b4e1@axiros.com> (raw)
In-Reply-To: <8783be66050414102551698d86@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 701 bytes --]

On 14.04.2005, at 19:25, Ross Biro wrote:

> Just to be clear, we can have two users A and B with the exact same
> hardware.  A setting of  =y will screw user A and a setting of =n will
> screw user B.  Ideally, they would both get better hardware, but that
> is not always an option.

You tell me a better[1] 32bit GigE PCI adapter than Intel E1000
and I sure do this. It's pretty interesting to see that those
who buy some not-so-cheeep hardware are being screwed in this
case; it should be in Intels best interest to help fix this
issue ASAP and permantently for all users.

[1] better performance at less CPU utilization + good diagnostics
     and negotiation capabilities

Servus,
       Daniel

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 186 bytes --]

      parent reply	other threads:[~2005-04-14 19:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-05 19:33 Ross Biro
2005-04-05 20:53 ` Randy.Dunlap
2005-04-06 12:47   ` Ross Biro
2005-04-06 20:44 ` Daniel Egger
2005-04-10 13:29 ` Andi Kleen
     [not found]   ` <8783be66050412075218b2b0b0@mail.gmail.com>
2005-04-13 18:37     ` Andi Kleen
2005-04-13 23:00       ` Ross Biro
2005-04-13 23:28         ` Dave Jones
2005-04-14 17:25           ` Ross Biro
2005-04-14 17:34             ` Tim Hockin
2005-04-14 18:02               ` Andi Kleen
2005-04-14 18:33                 ` Dave Jones
2005-04-14 19:14             ` Daniel Egger [this message]

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=d2274e05b0524222d01c2d584297b4e1@axiros.com \
    --to=de@axiros.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ross.biro@gmail.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

Powered by JetHome