public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@ecoscentric.com
To: ecos-bugs@sources.redhat.com
Subject: [Bug 1000347]  New: FreeBSD Network Thread misses incoming packet enque in ether_demux
Date: Sat, 09 Dec 2006 21:09:00 -0000	[thread overview]
Message-ID: <20061201095007.CACDC2C00B@snape.ecoscentric.com> (raw)

http://bugzilla.ecoscentric.com/show_bug.cgi?id=1000347

           Summary: FreeBSD Network Thread misses incoming packet enque in
                    ether_demux
           Product: eCos
           Version: unknown
          Platform: All
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: high
         Component: TCPIP
        AssignedTo: gary@mlbassoc.com
        ReportedBy: bugzilla_rmvthis@ds3switch.com
         QAContact: ecos-bugs@sources.redhat.com


If the priority of the ethernet driver thread is lower (higher #) than the FreeBSD Network Thread, then the Network Thread can get prematurely woken up to process an incoming ethernet pkt before the packet is fully enqued.  Specifically:

if_ethersubr:ether_demux() calls schednetisr() (which wakes up network thread) prior to the pkt being enqued with that call to IF_ENQUEUE().

This might not be obvious because a subsequent incoming packet can (partially) process the queue.

-- 
Configure bugmail: http://bugzilla.ecoscentric.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.


                 reply	other threads:[~2006-12-01  9:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20061201095007.CACDC2C00B@snape.ecoscentric.com \
    --to=bugzilla-daemon@ecoscentric.com \
    --cc=ecos-bugs@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).