kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Filka <mfilka@sitronics.com>
To: Stefan Weil <weil@mail.berlios.de>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: RE: eepro100.c
Date: Tue, 22 Sep 2009 06:50:19 +0200	[thread overview]
Message-ID: <BEE650D2F88D74448AD3E613B0C6D4E501092649CA@STS-PRG-EXM1M1.sts.sitronics.com> (raw)
In-Reply-To: <4AB510A1.9010702@mail.berlios.de>

Hi
> >
> > up to now, nobody complained about the missing RNR interrupts.
> > Linux obviously works without them, so I had no reason to
> > implement them.
... I'm not complaining, I'm asking for help ;-) Virtualization is working - no problem. However, it turns emulated driver into suspended state under heavy load (8 cores, 16 GB RAM, gigabit Ethernet - all cpu's at 100% due to network traffic processing by application in virtualizations) - my driver doesn't get any FR interrupts, when I issue a "ru resume" command (a timer) rx works again. 
> >
> > The disabled code parts (function eepro100_rnr_interrupt)
> > can be enabled, but you still need code which calls them
> > at the right places.
... sure
> >
> could you please try the appended patch and tell me whether it works?
... thank you. I'm going to try it today. I'll give you know then.
> 
Michal Filka


  reply	other threads:[~2009-09-22  4:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17  8:34 eepro100.c Michal Filka
2009-09-19 11:14 ` eepro100.c Jan Kiszka
2009-09-19 11:58   ` eepro100.c Stefan Weil
2009-09-19 17:10     ` eepro100.c Stefan Weil
2009-09-22  4:50       ` Michal Filka [this message]
2009-09-22  9:25       ` eepro100.c Michal Filka
2009-09-22 11:31       ` eepro100.c Michal Filka
2009-09-22 11:56         ` eepro100.c Amit Shah
2009-09-22 16:15           ` eepro100.c Stefan Weil
2009-09-23  5:34       ` eepro100.c Michal Filka

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=BEE650D2F88D74448AD3E613B0C6D4E501092649CA@STS-PRG-EXM1M1.sts.sitronics.com \
    --to=mfilka@sitronics.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=weil@mail.berlios.de \
    /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).