9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Tim Newsham <newsham@lava.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] allocb question
Date: Mon, 31 Jan 2005 18:49:52 -1000	[thread overview]
Message-ID: <Pine.BSI.4.61.0501311848210.23562@malasada.lava.net> (raw)
In-Reply-To: <ee9e417a05013120334ea16313@mail.gmail.com>

I'm allocating a block that has special alignment requirements.
I'm doing the following:

         Block *bp;

         bp = iallocb(EthBufSz + 64);
         if(bp)
                 bp->rp = (uchar*)ROUNDUP((ulong)bp->rp, 64);
         return bp;

which seems to work, but feels a little dirty.  Is this
the right way to do this or is there another mechanism
I should be using?

Tim N.


  reply	other threads:[~2005-02-01  4:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-01  3:48 [9fans] remove files in /srv YAMANASHI Takeshi
2005-02-01  4:06 ` arisawa
2005-02-01  4:33   ` Russ Cox
2005-02-01  4:49     ` Tim Newsham [this message]
2005-02-01 20:31     ` rog
2005-02-02 23:22       ` Bruce Ellis
2005-02-02 23:57         ` Charles Forsyth

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=Pine.BSI.4.61.0501311848210.23562@malasada.lava.net \
    --to=newsham@lava.net \
    --cc=9fans@cse.psu.edu \
    /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).