From: William Allen Simpson <william.allen.simpson@gmail.com>
To: netdev@vger.kernel.org
Subject: Re: query: tcpdump versus atomic?
Date: Wed, 14 Oct 2009 11:20:12 -0400 [thread overview]
Message-ID: <4AD5EC2C.6070005@gmail.com> (raw)
In-Reply-To: <4AD5522B.50101@gmail.com>
William Allen Simpson wrote:
> Anybody know what code path tcpdump changes to running atomic?
>
> Is there a function to test whether you're running atomic?
>
To partially answer my own question, after laboriously #if'ing compiling
section by section, it affects the tcp_minisockets.c code at
tcp_create_openreq_child().
I've not found a function to test. I've found sk->sk_allocation, but
that doesn't seem to be dynamically updated to reflect the current state.
Anyway, sorry David, but there's at least two GFP_ATOMIC here (one existing,
one new). I've managed to change the others, by careful rearrangement. At
least, I hope so, until some future testing reveals otherwise....
next prev parent reply other threads:[~2009-10-14 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 4:23 query: tcpdump versus atomic? William Allen Simpson
2009-10-14 15:20 ` William Allen Simpson [this message]
2009-10-14 15:59 ` Stephen Hemminger
2009-10-14 20:36 ` William Allen Simpson
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=4AD5EC2C.6070005@gmail.com \
--to=william.allen.simpson@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).