All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@bytesex.org>
To: Xen Development List <xen-devel@lists.xensource.com>
Subject: Re: [Xen-changelog] Add a /proc interface for setting rx-buffer allocation policy in
Date: 03 May 2005 13:31:31 +0200	[thread overview]
Message-ID: <87wtqg4kbw.fsf@bytesex.org> (raw)
In-Reply-To: <E1DSvAn-00020G-Ow@moria.surriel.com>

BitKeeper Bot <riel@surriel.com> writes:

> ChangeSet 1.1159.256.110, 2005/05/03 11:54:00+01:00, kaf24@firebug.cl.cam.ac.uk
> 
> 	Add a /proc interface for setting rx-buffer allocation policy in
> 	the netfront driver.
> 	e.g., 'echo 256 >/proc/xen/net/eth0/rxbuf_min' will avoid unnecessary
> 	packet drops by always allocating the maximum possible number of
> 	buffers at all times, at the expense of extra memory usage when the
> 	interface is idle.

Be prepared to be flamed for that on lkml, using /proc for stuff like
that (i.e. driver specifix settings) is depricated these days.  It
should go to sysfs instead.

I can come up with a patch for that, might take some days though as
I'm busy with some non-xen stuff at the moment.

cheers,

  Gerd

btw: can whoever runs the changelog list (rik?) please add the
repository (2.0, unstable, ...) to to subject line please?  And while
you are at it: -p1 for the diffstat would be cool as well, especially
for one-file commits, there are -- for example -- plenty of page.h
files in the tree.  Thanks.

-- 
#define printk(args...) fprintf(stderr, ## args)

       reply	other threads:[~2005-05-03 11:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1DSvAn-00020G-Ow@moria.surriel.com>
2005-05-03 11:31 ` Gerd Knorr [this message]
2005-05-03 12:21   ` Re: [Xen-changelog] Add a /proc interface for setting rx-buffer allocation policy in Keir Fraser

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=87wtqg4kbw.fsf@bytesex.org \
    --to=kraxel@bytesex.org \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.