From owner-freebsd-hackers Thu Sep 23 10:23:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailer.syr.edu (mailer.syr.edu [128.230.18.29]) by hub.freebsd.org (Postfix) with ESMTP id 9E783153D6 for ; Thu, 23 Sep 1999 10:23:11 -0700 (PDT) (envelope-from cmsedore@mailbox.syr.edu) Received: from rodan.syr.edu by mailer.syr.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.ADA86120@mailer.syr.edu>; Thu, 23 Sep 1999 13:22:26 -0400 Received: from localhost (cmsedore@localhost) by rodan.syr.edu (8.8.7/8.8.7) with ESMTP id NAA03646 for ; Thu, 23 Sep 1999 13:22:23 -0400 (EDT) X-Authentication-Warning: rodan.syr.edu: cmsedore owned process doing -bs Date: Thu, 23 Sep 1999 13:22:23 -0400 (EDT) From: Christopher Sedore X-Sender: cmsedore@rodan.syr.edu To: freebsd-hackers@freebsd.org Subject: mbufs, external storage, and MFREE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have the following question: Let's say that I have a block of user memory which I've mapped into the kernel, and would like to send on a network socket. I'd like to simply grab an mbuf, point to the memory as external storage, and queue it up for transmission. This would work fine, except that when MFREE gets called, I have to write an deallocator that maintains a table of all the different cases where I've done this, and do a reverse mapping back to the original block, and then deal with sending more, unmapping, etc. In other words, having MFREE call a deallocator with just the data pointer and the size is inconvenient (actually, it would make my scenario quite inefficient given the number of mappings back to the original block that would have to be done). Am I missing another mechanism to handle this? Does it not come up enough to matter? -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message