From: Andi Kleen <ak@suse.de>
To: "Jens Hoffrichter" <HOFFRICH@de.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: printk and sk_buffs
Date: 27 Jun 2001 17:38:20 +0200 [thread overview]
Message-ID: <oup7kxy3pcj.fsf@pigdrop.muc.suse.de> (raw)
In-Reply-To: <OFC7C24EA9.6CB8EE5C-ONC1256A78.004CC2C0@de.ibm.com.suse.lists.linux.kernel>
In-Reply-To: "Jens Hoffrichter"'s message of "27 Jun 2001 16:07:46 +0200"
"Jens Hoffrichter" <HOFFRICH@de.ibm.com> writes:
> I do not fully unterstandt the printk code, so perhaps somebody can answer
> me this (probably stupid ;) ) question:
>
> If I do a printk, is there a packet (aka a sk_buff) created? If I turn on
> debugging in my code, I see a huge pile of sk_buffs which are allocated but
> which do not get in touch with the "essential" parts of the network-code
> (e.g. ip_rcv) where I have modified some code. I can't explain it to me
> fully, but perhaps someone of yours has a suitable answer.
klogd uses unix sockets to talk to syslogd. unix sockets use sk_buffs.
You can kill klogd if you're not interested in logging kernel messages to disk.
-Andi
next parent reply other threads:[~2001-06-27 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OFC7C24EA9.6CB8EE5C-ONC1256A78.004CC2C0@de.ibm.com.suse.lists.linux.kernel>
2001-06-27 15:38 ` Andi Kleen [this message]
2001-07-27 14:02 Jens Hoffrichter
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=oup7kxy3pcj.fsf@pigdrop.muc.suse.de \
--to=ak@suse.de \
--cc=HOFFRICH@de.ibm.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
all inboxes | Powered by JetHome®